X-Git-Url: http://git.samba.org/?a=blobdiff_plain;f=README.Coding;h=2e7dd2f3f245991caa75c17d783a92bd85113f62;hb=8d88de0c5fa4836c163e4588b5a58d8ff607e05f;hp=fd52dbe890d6b870b7bcfa77b528224debc762f2;hpb=a4137c3555562b7a2ad558ed3849b1dfa10cb845;p=samba.git diff --git a/README.Coding b/README.Coding index fd52dbe890d..2e7dd2f3f24 100644 --- a/README.Coding +++ b/README.Coding @@ -1,43 +1,42 @@ -## -## Coding conventions in the Samba 3.0 tree -## +Coding conventions in the Samba tree +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. contents:: =========== Quick Start =========== Coding style guidelines are about reducing the number of unnecessary -reformatting patches and making things easier developers to work together. +reformatting patches and making things easier for developers to work together. You don't have to like them or even agree with them, but once put in place we all have to abide by them (or vote to change them). However, coding -style should never outweigh coding itself and so the the guidelines -described here are hopefully easier enough to follow as they are very +style should never outweigh coding itself and so the guidelines +described here are hopefully easy enough to follow as they are very common and supported by tools and editors. -The basic style, also mentioned in the SAMBA_4_0/prog_guide.txt is the -Linux kernel coding style (See Documentation/CodingStyle in the kernel -source tree). The closely matches what most Samba developers use already -anyways. +The basic style, also mentioned in prog_guide4.txt, is the Linux kernel coding +style (See Documentation/CodingStyle in the kernel source tree). This closely +matches what most Samba developers use already anyways. But to save you the trouble of reading the Linux kernel style guide, here are the highlights. - * Maximum Line Width is 80 Characters The reason is not for people with low-res screens but rather sticking to 80 columns prevents you from easily nesting more than one level of - if statements or other code blocks. Use source/script/count_80_col.pl + if statements or other code blocks. Use source3/script/count_80_col.pl to check your changes. * Use 8 Space Tabs to Indent No whitespace filler. * No Trailing Whitespace - Use source/script/strip_trail_ws.pl to clean you files before committing. + Use source3/script/strip_trail_ws.pl to clean you files before committing. * Follow the K&R guidelines. We won't go throw them all here. You have a copy of "The C Programming Language" anyways right? You can also use - the format_indent.sh script found in source/script/ if all else fails. + the format_indent.sh script found in source3/script/ if all else fails. @@ -59,14 +58,14 @@ Vi -- (Thanks to SATOH Fumiyasu for these hints): -For the basic vi editor including with all variants of *nix, add the +For the basic vi editor included with all variants of \*nix, add the following to $HOME/.exrc: set tabstop=8 set shiftwidth=8 For Vim, the following settings in $HOME/.vimrc will also deal with -displaying trailing whitespace: +displaying trailing whitespace:: if has("syntax") && (&t_Co > 2 || has("gui_running")) syntax on @@ -91,7 +90,7 @@ FAQ & Statement Reference Comments -------- -Comments should always use the standard C syntax. I.e. /* ... */. C++ +Comments should always use the standard C syntax. C++ style comments are not currently allowed. @@ -100,7 +99,7 @@ Indention & Whitespace & 80 columns To avoid confusion, indentations are to be 8 character with tab (not 8 ' ' characters. When wrapping parameters for function calls, -alignment parameter list with the first parameter on the previous line. +align the parameter list with the first parameter on the previous line. Use tabs to get as close as possible and then fill in the final 7 characters or less with whitespace. For example, @@ -133,7 +132,7 @@ Note that this is a rule about parentheses following keywords and not functions. Don't insert a space between the name and left parentheses when invoking functions. -Braces for code blocks used by for, if, switch, while, do..while, etc... +Braces for code blocks used by for, if, switch, while, do..while, etc. should begin on the same line as the statement keyword and end on a line of their own. NOTE: Functions are different and the beginning left brace should begin on a line of its own. @@ -145,7 +144,7 @@ The exception to the ending rule is when the closing brace is followed by another language keyword such as else or the closing while in a do..while loop. -Good examples: +Good examples:: if (x == 1) { printf("good\n"); @@ -162,7 +161,7 @@ Good examples: printf("also good\n"); } while (1); -Bad examples: +Bad examples:: while (1) { @@ -173,33 +172,33 @@ Goto ---- While many people have been academically taught that goto's are fundamentally -evil, then can greatly enhance readability and reduce memory leaks when used +evil, they can greatly enhance readability and reduce memory leaks when used as the single exit point from a function. But in no Samba world what so ever is a goto outside of a function or block of code a good idea. -Good Examples: - -int function foo(int y) -{ - int *z = NULL; - int ret = 0; +Good Examples:: - if ( y < 10 ) { - z = malloc(sizeof(int)*y); - if (!z) { - ret = 1; - goto done; + int function foo(int y) + { + int *z = NULL; + int ret = 0; + + if ( y < 10 ) { + z = malloc(sizeof(int)*y); + if (!z) { + ret = 1; + goto done; + } } - } - print("Allocated %d elements.\n", y); + print("Allocated %d elements.\n", y); - done: - if (z) - free(z); + done: + if (z) + free(z); - return ret; -} + return ret; + } Checking Pointer Values @@ -207,13 +206,13 @@ Checking Pointer Values When invoking functions that return pointer values, either of the following are acceptable. Use you best judgement and choose the more readable option. -Remember that many other people will review it. +Remember that many other people will review it.:: if ((x = malloc(sizeof(short)*10)) == NULL ) { fprintf(stderr, "Unable to alloc memory!\n"); } -or +or:: x = malloc(sizeof(short)*10); if (!x) {