manual:coding_style_guide
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
manual:coding_style_guide [2015/07/16 16:33] – Making Class naming rules more specific zenke | manual:coding_style_guide [2017/01/08 02:46] – Fixes broken link zenke | ||
---|---|---|---|
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:// | + | [[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. 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 15:08 by zenke