manual:coding_style_guide
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
manual:coding_style_guide [2015/07/02 18:17] – zenke | manual:coding_style_guide [2015/07/16 16:33] – Making Class naming rules more specific zenke | ||
---|---|---|---|
Line 9: | Line 9: | ||
**Class names** should be in CamelCase starting with a capital letter. Classes should be defined in their own .h .cpp file combination which should carry the same names and case. | **Class names** should be in CamelCase starting with a capital letter. Classes should be defined in their own .h .cpp file combination which should carry the same names and case. | ||
+ | |||
+ | * Classes deriving from [[SpikingGroup]] should have name ending in Group (e.g. [[TIFGroup]]) | ||
+ | * Classes deriving from [[Connection]] should have name ending in Connection (e.g. [[SparseConnection]]) | ||
+ | * Classes deriving from [[Monitor]] should have name ending in Monitor (e.g. [[SpikeMonitor]]) | ||
**Class instances** either variable case or camel case with the first letter being a small letter. | **Class instances** either variable case or camel case with the first letter being a small letter. | ||
**Macro names** ALL_CAPS_WITH_UNDERSCORES | **Macro names** ALL_CAPS_WITH_UNDERSCORES |
manual/coding_style_guide.txt · Last modified: 2018/05/18 15:08 by zenke