On Friday 25 February 2005 05:56, Nathan Folkman wrote: > i recommend that you follow the aolserver style guide, which is heavily > based on the tcl style guide. however, when in doubt, it is best to > follow the style you see in the core code, as almost all of it is > consistently formatted. it shouldn't be too difficult to infer the > style by looking at a few different source files.
Okay, I have taken the time to browse several source files. I think the cleanest I have found is binder.c, but it still has several styles, or inconsistencies. I'm talking only about whitespace here, not any of the naming conventions, or broader considerations. So I'm really stuck wondering what to do. The source files differ in substantial ways from the written guides. The source files differ from each other, and each file itself represents several styles. I had the timely fortune of needing to replace my crashed hard drive this weekend and I noticed a program being installed called 'indent'. Indent is a program which reformats the whitespace of C source code. Given a series of switches, which can be maintained in a file, it can help developers transform the files they are working on into a consistent style. It seems to have enough switches to handle more than has ever been covered in either of the written guides. I'm sure there are downsides, but it sounds like a good way to document one small aspect of the development standards for AOLserver. Has anyone had good or bad experiences with this tool? tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
