home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!srhqla!quest!kdq
- From: kdq@quest.UUCP (Kevin D. Quitt)
- Newsgroups: comp.lang.c
- Subject: Re: The Correct Way To Write C if-Statements
- Message-ID: <cmsXTB1w165w@quest.UUCP>
- Date: Sun, 08 Nov 92 12:11:47 PST
- References: <140797@lll-winken.LLNL.GOV>
- Reply-To: srhqla!quest!kdq
- Organization: Job quest (805) 251-8210, So Cal: (800) 400-8210
- Lines: 19
-
- The only reasonable way I've ever found to maintain code appearance
- consistency within a group is to use Gnu's indent or other reformatter.
- When a person checks in his/her code, it's run through indent with a
- preselected set of parameters to control the format. Thus, any code
- checked out will be uniform in appearance.
-
- On the other hand, since this annoys the programmers who have their
- own style, there's an option that lets them have the check-out process
- automatically reformat a piece of code using their selected parameters.
-
- This way keeps the programmers happy, and keeps whoever decided
- there needs to be a consistent style happy.
-
-
- _
- Kevin D. Quitt Job Quest (805) 251-8210
- srhqla!quest!kdq Learn How to Get a Job in SoCal
-
- 96.37% of all statistics are made up.
-