summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2007-09-06 11:08:23 +0000
committerDaniel Stenberg <daniel@haxx.se>2007-09-06 11:08:23 +0000
commit8e757340834bb7e377affa50bfba809e967bcbaa (patch)
tree176bc645ac6d917088009888084012ddd359a4ef /docs
parentdb4753e92445d1a6008e8bf6ab6afdfc12ff874a (diff)
downloadrockbox-8e757340834bb7e377affa50bfba809e967bcbaa.tar.gz
rockbox-8e757340834bb7e377affa50bfba809e967bcbaa.zip
mention the brace placement for functions
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@14627 a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'docs')
-rw-r--r--docs/CONTRIBUTING7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/CONTRIBUTING b/docs/CONTRIBUTING
index 1bd055860b..d36e359719 100644
--- a/docs/CONTRIBUTING
+++ b/docs/CONTRIBUTING
@@ -44,6 +44,13 @@ When changing code, follow the code style of the file you are editing.
44 44
45When writing new files, you may use the brace placement style of your choice. 45When writing new files, you may use the brace placement style of your choice.
46 46
47Braces for function declarations are put in a new line under the name, as in:
48
49 int foo(char *name)
50 {
51 return FOO_NAME:
52 }
53
47Always indent your code with four spaces. Don't use TAB characters, as that 54Always indent your code with four spaces. Don't use TAB characters, as that
48will mess up code display in CVS, printing, and a zillion other places. 55will mess up code display in CVS, printing, and a zillion other places.
49 56