summaryrefslogtreecommitdiffstats
path: root/cervisia/HACKING
blob: dfa61cddef184b2054de5a6ff8a600adf9ac77ea (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Coding Style
============

Formatting
----------

- No tabs.
- Indent is 4 spaces.
- A line should not exceed 80 chars.
- Brackets are always on separate lines.
- Put spaces between brackets of if, while and
  similar statements.
  
  
Example:

void MyClass::myFunction(const QString& arg)
{
    if( blah == "halb" )
    {
        doSometing();
    }
    else
    {
        varA = varB;
    }
}



Header Formatting
-----------------

- Access modifiers are not indented.
- Double inclusion guard defines are all upper case
  letters and are composed of the namespace (if available),
  the classname and a H suffix separated by underscores.
- Inside a namespace there is no indentation.

  
Example:

#ifndef NAMESPACE_MYCLASS_H
#define NAMESPACE_MYCLASS_H

namespace Namespace 
{

class MyClass
{
public:
    MyClass();
    
private:
    int       m_intVar;
    KProcess* m_proc;
};

}

#endif



Class and File Names
--------------------



Class and Variable Names
------------------------

- For class, variable and function names separate multiple
  words by uppercasing the words preceded by other words.
- Class names start with an uppercase letter.
- Function names start with a lowercase letter.
- Variable names start with a lowercase letter.
- Member Variables of a class start with a 'm_' prefix
  followed by an lowercase letter.