3 \page coding_style LEMON Coding Style
5 \section naming_conv Naming Conventions
7 In order to make development easier we have made some conventions
8 according to coding style. These include names of types, classes,
9 functions, variables, constants and exceptions. If these conventions
10 are met in one's code then it is easier to read and maintain
11 it. Please comply with these conventions if you want to contribute
12 developing LEMON library.
14 \subsection cs-class Classes and other types
16 The name of a class or any type should look like the following:
19 AllWordsCapitalizedWithoutUnderscores
22 \subsection cs-func Methods and other functions
24 The name of a function should look like the following:
27 firstWordLowerCaseRestCapitalizedWithoutUnderscores
30 \subsection cs-funcs Constants, Macros
32 The names of constants and macros should look like the following:
35 ALL_UPPER_CASE_WITH_UNDERSCORES
38 \subsection cs-loc-var Class and instance member variables, auto variables
40 The names of class and instance member variables and auto variables (=variables used locally in methods) should look like the following:
43 all_lower_case_with_underscores
46 \subsection cs-excep Exceptions
48 When writing exceptions please comply the following naming conventions:
51 ClassNameEndsWithException
54 \warning In some cases we diverge from these rules.
55 This primary done because STL uses different naming convention and
57 it is beneficial to provide STL compatible interface.