On Thu, 2 Oct 2008, Paul Thomas wrote: > Ok, I'll make sure and update the docs in the CVS tree. Also, I'll take care > of the faults you listed below tonight (10-12hrs from now). Before I make > any other commits, are their any other general guidelines I should know > about? I assumed that people normally follow the same coding style to keep a > uniform appearence.
Yeah, after discussions we agreed on the indent style we currently use. > What length do you normally keep tabs at and do you convert tabs to spaces? These are the 'indent' options we used: indent \ --braces-on-if-line \ --braces-after-struct-decl-line \ --space-after-cast \ --line-length 79 \ --comment-line-length 79 \ --cuddle-else \ --no-tabs \ --tab-size 8 \ --indent-level 4 \ --no-space-after-for \ --space-after-if \ --space-after-while \ --no-space-after-function-call-names > Anything else you can think of? Portability is important. C89 is the standard level. -- / daniel.haxx.se ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
