summaryrefslogtreecommitdiff
path: root/source3/CodingSuggestions
diff options
context:
space:
mode:
Diffstat (limited to 'source3/CodingSuggestions')
-rw-r--r--source3/CodingSuggestions16
1 files changed, 2 insertions, 14 deletions
diff --git a/source3/CodingSuggestions b/source3/CodingSuggestions
index e5f366ec71..eda2bee6d0 100644
--- a/source3/CodingSuggestions
+++ b/source3/CodingSuggestions
@@ -25,11 +25,7 @@ documents are:
http://www.fsf.org/prep/standards_toc.html
but note that coding style in Samba varies due to the many different
-programmers who have contributed.
-
-The indent utility can be used to format C files in the general
-samba coding style. The arguments you should give to indent are:
--bad -bap -br -ce -cdw -nbc -brs -bbb -nbc -npsl
+programmers who have contributed.
Following are some considerations you should use when adding new code to
Samba. First and foremost remember that:
@@ -141,20 +137,12 @@ Here are some other suggestions:
to and maintain your code. If it would be hard for someone else to
maintain then do it another way.
-26) Always keep the declaration of a function on one line. The autoprototyper
- doesn't catch declarations spread over multiple lines.
- Use:
-static char foo(int bar)
- and not:
-static char
-foo(int bar)
-
The suggestions above are simply that, suggestions, but the information may
help in reducing the routine rework done on new code. The preceeding list
is expected to change routinely as new support routines and macros are
added.
Written by Steve French, with contributions from Simo Sorce, Andrew
-Bartlett, Tim Potter, Martin Pool and Jelmer Vernooij.
+Bartlett, Tim Potter and Martin Pool.
**/