Thread View: comp.unix.programmer
2 messages
2 total messages
Started by John Tamplin
Wed, 17 Oct 1990 18:34
Re: Catch Source Code Errors - Tricks Wanted
Author: John Tamplin
Date: Wed, 17 Oct 1990 18:34
Date: Wed, 17 Oct 1990 18:34
25 lines
1630 bytes
1630 bytes
This is sortof off the subject, but one problem I have always had when working on team projects was differences in coding style. Typically each person wrote in their own style, so you wound up with a mess of different styles which really makes the code hard to read. Sometimes, people would reformat bits of code (usually fixes applied by someone else) to their own style, something that especially trashes RCS-type programs, since there are a lot of changes to lines in the program that aren't changes as far as the compiler is concerned. A tool I have always wanted to build, but have never had (made) time for is this: a version of RCS which canonicalizes (is that a word?) the source as it is checked in. When a user checks out a ocpy of the file, the program checks an environment variable or some ~/.xxx file to discover the user's style preferences. That way, each person can inspect code in their favorite style, without impacting any other team members' ability to do the same. The file could be stored as a normal program, or the version control system might choose to store it in some kind of tokenized form to ease reassembly into different styles. Maybe one of these days I will actually write it. -- John Tamplin Xavax jat@xavax.COM 2104 West Ferry Way ...!uunet!xavax!jat Huntsville, AL 35801
Re: Catch Source Code Errors - Tricks Wanted
Author: Paul Chamberlain
Date: Thu, 18 Oct 1990 20:12
Date: Thu, 18 Oct 1990 20:12
17 lines
1517 bytes
1517 bytes
In article <1990Oct17.183455.12233@xavax.com> jat@xavax.com (John Tamplin) writes: >A tool I have always wanted to build, but have never had (made) time for is >this: a version of RCS which canonicalizes (is that a word?) the source as >it is checked in. When a user checks out a ocpy of the file, the program >checks an environment variable or some ~/.xxx file to discover the user's style >preferences. It seems like you could build this with the normal RCS and "indent". As long as the programmer's style can be represented by indent options you're in luck. "indent" it in one style and stuff it in RCS. When it is checked out, "indent" it in the programmers style. The only real work necessary might be a few changes to indent to fit your exact desires. Anybody done this? I'm tempted because people around here indent w/spaces. Paul Chamberlain | I do NOT represent IBM. tif@doorstop, sc30661 at ausvm6 512/838-7008 | ...!cs.utexas.edu!ibmaus!auschs!doorstop.austin.ibm.com!tif
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads