manual:coding_style_guide
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
manual:coding_style_guide [2015/07/02 18:14] – created zenke | manual:coding_style_guide [2015/07/02 18:17] – zenke | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Naming conventions ====== | ====== Naming conventions ====== | ||
- | On the long the Auryn code should follow Googles naming conventions because there seems to be some kind of 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:// | [[https:// | ||
- | 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