Auryn simulator

Simulator for spiking neural networks with synaptic plasticity

User Tools

Site Tools


manual:coding_style_guide

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
manual:coding_style_guide [2015/07/16 18:33]
zenke Making Class naming rules more specific
manual:coding_style_guide [2017/01/08 03:46]
zenke Fixes broken link
Line 2: Line 2:
  
 On the long the Auryn code should follow Googles naming conventions because there seems to be to some degree a consensus on those. On the long the Auryn code should follow Googles naming conventions because there seems to be to some degree a consensus on those.
-[[https://​google-styleguide.googlecode.com/svn/trunk/​cppguide.html]]+[[https://​google.github.io/styleguide/​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. The most important deviation concerns file names which are so far all in CamelCase. ​ 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. ​
manual/coding_style_guide.txt ยท Last modified: 2018/05/18 17:08 by zenke