Coding Guidelines

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m (revert vandalism)
m
Line 21: Line 21:
 
== Commit Logs ==
 
== Commit Logs ==
 
[http://www.gnu.org/prep/standards/html_node/Change-Logs.html GNU Change Log Guidelines]
 
[http://www.gnu.org/prep/standards/html_node/Change-Logs.html GNU Change Log Guidelines]
 +
 +
 +
<span id="bottom"></span>
 +
{{Languages|Coding_Guidelines}}

Revision as of 11:07, 11 July 2007

Contents

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


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