[asterisk-commits] branch kpfleming/chanfunc r9673 - /team/kpfleming/chanfunc/doc/CODING-GUIDELINES

[asterisk-commits at lists.digium.com]

Author: kpfleming
Date: Sat Feb 11 22:24:26 2006
New Revision: 9673

URL: http://svn.digium.com/view/asterisk?rev=9673&view=rev
Log:
minor update to indent parameters

Modified:
    team/kpfleming/chanfunc/doc/CODING-GUIDELINES

Modified: team/kpfleming/chanfunc/doc/CODING-GUIDELINES
URL: http://svn.digium.com/view/asterisk/team/kpfleming/chanfunc/doc/CODING-GUIDELINES?rev=9673&r1=9672&r2=9673&view=diff
==============================================================================
--- team/kpfleming/chanfunc/doc/CODING-GUIDELINES (original)
+++ team/kpfleming/chanfunc/doc/CODING-GUIDELINES Sat Feb 11 22:24:26 2006
@@ -77,7 +77,7 @@
 Roughly, Asterisk code formatting guidelines are generally equivalent to the 
 following:
 
-# indent -i4 -ts4 -br -brs -cdw -cli0 -ce -nbfda -npcs -nprs -npsl -saf -sai -saw foo.c
+# indent -i4 -ts4 -br -brs -cdw -lp -ce -nbfda -npcs -nprs -npsl -nbbo -saf -sai -saw -cs -ln90 foo.c
 
 this means in verbose:
  -i4:    indent level 4
@@ -85,7 +85,7 @@
  -br:    braces on if line
  -brs:   braces on struct decl line
  -cdw:   cuddle do while
- -cli0:  case indentation 0
+ -lp:    line up continuation below parenthesis
  -ce:    cuddle else
  -nbfda: dont break function decl args
  -npcs:  no space after function call names
@@ -94,6 +94,8 @@
  -saf:   space after for
  -sai:   space after if
  -saw:   space after while
+ -cs:    space after cast
+ -ln90:  line length 90 columns
 
 Function calls and arguments should be spaced in a consistent way across
 the codebase.