Auryn simulator

Simulator for spiking neural networks with synaptic plasticity

User Tools

Site Tools

Trace:
manual:coding_style_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
manual:coding_style_guide [2015/07/02 18:16] – zenkemanual:coding_style_guide [2015/07/02 18:17] – zenke
Line 4: Line 4:
 [[https://google-styleguide.googlecode.com/svn/trunk/cppguide.html]] [[https://google-styleguide.googlecode.com/svn/trunk/cppguide.html]]
  
-However, currently the code only enforces these conventions in part. Here are some naming conventions in Auryn which seem to have emerged over the years. Most of them are in line with the Google style.+However, currently the code only enforces these conventions in part. Here are some naming conventions in Auryn which seem to have emerged over the years. Most of them are in line with the Google style. The most important deviation concerns file names which are so far all in CamelCase. 
  
 **Variable names** in the code should be named all lower case with underscores_where_necessary. **Variable names** in the code should be named all lower case with underscores_where_necessary.
manual/coding_style_guide.txt · Last modified: 2018/05/18 15:08 by zenke