Coding Guidelines

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(catchg)
 
(5 intermediate revisions by 4 users not shown)
Line 17: Line 17:
  
 
== C++ Coding ==
 
== C++ Coding ==
[http://www.zen.uci.edu/~klefstad/s/C++-style.html C++ Style Guidelines]
+
* [http://www.zen.uci.edu/~klefstad/s/C++-style.html C++ Style Guidelines]
 +
* [http://en.wikibooks.org/wiki/C++_Programming/Code_Style C++ Programming Code Style (WikiBooks)]
  
 
== Commit Logs ==
 
== Commit Logs ==
Line 26: Line 27:
 
{{Languages|Coding_Guidelines}}
 
{{Languages|Coding_Guidelines}}
  
[[Category:Categories]]
+
[[Category:Developer resources]]

Latest revision as of 12:20, 19 July 2009

Contents

[edit] General Recommendations

GNU Standards is also a good read for developers in general.

[edit] C Coding

All C code should be done in the C99 standard -- it's much more maintainable, less error prone, clean and concise, and removes a lot of C's warts.

Here is some good information about C99:

This is a good C coding guide:

[edit] C++ Coding

[edit] Commit Logs

GNU Change Log Guidelines


Personal tools

General Recommendations

GNU Standards is also a good read for developers in general.

C Coding

All C code should be done in the C99 standard -- it's much more maintainable, less error prone, clean and concise, and removes a lot of C's warts.

Here is some good information about C99:

This is a good C coding guide:

C++ Coding

C++ Style Guidelines

Commit Logs

GNU Change Log Guidelines