Coding Guidelines
From Openmoko
(Difference between revisions)
m |
m (Reverted vandalism) |
||
| Line 16: | Line 16: | ||
* [http://developer.gnome.org/doc/guides/programming-guidelines/book1.html GNOME Programming Guidelines] | * [http://developer.gnome.org/doc/guides/programming-guidelines/book1.html GNOME Programming Guidelines] | ||
| − | == C | + | == C++ Coding == |
| − | [http://www.zen.uci.edu/~klefstad/s/C | + | [http://www.zen.uci.edu/~klefstad/s/C++-style.html C++ Style Guidelines] |
== 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] | ||
Revision as of 00:57, 12 April 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:
- http://www-128.ibm.com/developerworks/linux/library/l-c99.html?ca=dgr-lnxw07UsingC99
- http://en.wikipedia.org/wiki/C_programming_language#C99
This is a good C coding guide:
