Changeset 614:75cf1d52eee5 in lemon-0.x for doc/coding_style.dox
- Timestamp:
- 05/11/04 21:38:00 (21 years ago)
- Branch:
- default
- Phase:
- public
- Convert:
- svn:c9d7d8f5-90d6-0310-b91f-818b3a526b0e/lemon/trunk@799
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/coding_style.dox
r603 r614 7 7 In order to make development easier we have made some conventions according to coding style. These include names of types, classes, functions, variables, constants and exceptions. If these conventions are met in one's code then it is easier to read and maintain it. Please comply with these conventions if you want to contribute developing Hugo library. 8 8 9 \subsection Classes and other types9 \subsection cs-class Classes and other types 10 10 11 11 The name of a class or any type should look like the following: … … 15 15 \endcode 16 16 17 \subsection Methods and other functions17 \subsection cs-func Methods and other functions 18 18 19 19 The name of a function should look like the following: … … 23 23 \endcode 24 24 25 \subsection Constants, Macros25 \subsection cs-funcs Constants, Macros 26 26 27 27 The names of constants and macros should look like the following: … … 31 31 \endcode 32 32 33 \subsection Class and instance member variables, auto variables33 \subsection cs-loc-var Class and instance member variables, auto variables 34 34 35 35 The names of class and instance member variables and auto variables (=variables used locally in methods) should look like the following: … … 39 39 \endcode 40 40 41 \subsection Exceptions41 \subsection cs-excep Exceptions 42 42 43 43 When writing exceptions please comply the following naming conventions:
Note: See TracChangeset
for help on using the changeset viewer.