Changeset 603:86458ad390a7 in lemon-0.x for doc/coding_style.dox

Timestamp:

05/11/04 11:30:06 (21 years ago)

Author:

athos

Branch:

default

Phase:

public

Convert:

svn:c9d7d8f5-90d6-0310-b91f-818b3a526b0e/lemon/trunk@784

Message:

I completed the description of the coding style.

File:

• doc/coding_style.dox (modified) (5 diffs)

doc/coding_style.dox

@@ -3 +3 @@
 \page coding_style Hugo Coding Style 
 
-\todo More detailed description, an introductory paragraph, etc.
- 
-\section Naming Convenions
+\section Naming Conventions
 
-\subsection Classes
+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. 
+
+\subsection Classes and other types
+
+The name of a class or any type should look like the following:
 
 \code
@@ -13 +15 @@
 \endcode
 
-\subsection Methods
+\subsection Methods and other functions
+
+The name of a function should look like the following:
 
 \code
@@ -19 +23 @@
 \endcode
 
-\subsection Constants
+\subsection Constants, Macros
+
+The names of constants and macros should look like the following:
 
 \code
@@ -25 +31 @@
 \endcode
 
-\subsection %Class and instance member variables
+\subsection Class and instance member variables, auto variables 
 
-\code
-all_lower_case_with_underscores 
-\endcode
-
-\subsection Auto variables (=variables used locally in methods)
+The names of class and instance member variables and auto variables (=variables used locally in methods) should look like the following:
 
 \code
@@ -39 +41 @@
 \subsection Exceptions
 
+When writing exceptions please comply the following naming conventions:
+
 \code
 ClassNameEndsWithException