christoph/fail
1
Fork 0
Code Releases Activity

Tiny updates in Coding-Style guideline.

Browse Source 
git-svn-id: https://www4.informatik.uni-erlangen.de/i4svn/danceos/trunk/devel/fail@1317 8c4709b5-6ec9-48aa-a5cd-a96041d1645a
This commit is contained in:
adrian
2012-06-07 17:41:08 +00:00
parent 715a393598
commit 33154a35c4
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/coding-style.txt
View File

@ -8,7 +8,7 @@ For Python code, try to stick to <http://www.python.org/dev/peps/pep-0008>.
Especially use 4 spaces per indentation level, and don't mix tabs and spaces
for indentation.
The following style rules apply to C/C++ code:
The following style rules apply to C/C++/AspectC++ code:
- Language (comments, SVN commit messages, "temporary" stuff): English
(without exception)
@ -56,7 +56,7 @@ The following style rules apply to C/C++ code:
class Foo {
public:
<TAB>void doSomething();
}
};
Similarly (and for the same reason) for namespaces and switch/case
statements:
switch (foo) {
@ -69,14 +69,14 @@ The following style rules apply to C/C++ code:
if (something) {
<TAB>...
}
* Function definitions are an exception to this ('{' in a new line):
* Method/Function definitions are an exception to this ('{' in a new line):
Definition: | Declaration:
void myFunction(int i) | void myFunction(int i);
{ |
<TAB>... |
} |
* Control structure tokens ("if", "try", ...) are followed by a single
space for better disambiguation from function definitions:
* Control structure tokens ("if", "try", for, ...) are followed by a
single space for better disambiguation from function definitions:
if (...) {
<TAB>...
} else if (...) {