Changes between Version 3 and Version 4 of CodingStyle

Timestamp:

Dec 16, 2011, 2:36:11 PM (14 years ago)

Author:

Matthias Vogelgesang

Comment:

--

CodingStyle

@@ -3 +3 @@
 In general, the [http://kerneltrap.org/files/Jeremy/CodingStyle.txt coding standards] used in the Linux kernel are versatile, comprehensive and quite good looking. They are boiling down to the following guide lines:
 
- Indentation:: Spaces
+ Indentation:: Four spaces
  Spaces:: Spaces around keywords but not in inner parenthesis.
  Brace placement:: '{' at end of line except for function definition and '}' on its own line except in do-while-loops.
  Naming:: Descriptive for global functions and usually lower case with underscores.
  Macros:: Upper case for constants, lower case with underscores for macros resembling functions.
- Structures:: No typedefs, although this is debatable. For shared data structures reference counting should be implemented.
+ Structures:: Consistency when using typedefs or not. For shared data structures reference counting should be implemented.
 
 I would add the following:
@@ -19 +19 @@
 There are still some open questions:
 
-* Number of white lines to separate functions?
+* Number of newlines to separate functions?
 * Comments: C vs. C++ style, usage of '*'?
 * Alignment of multiple assignments?
@@ -56 +56 @@
 }}}
 
-
 == Astyle Formatter ==