Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!romp!auschs!awdprime!doorstop.austin.ibm.com!tif
From: tif@doorstop.austin.ibm.com (Paul Chamberlain)
Newsgroups: comp.unix.programmer
Subject: Re: Catch Source Code Errors - Tricks Wanted
Message-ID: <3934@awdprime.UUCP>
Date: 18 Oct 90 20:12:09 GMT
References: <1990Oct17.183455.12233@xavax.com>
Sender: news@awdprime.UUCP
Reply-To: tif@doorstop.austin.ibm.com (Paul Chamberlain)
Organization: IBM AWD, Austin, TX
Lines: 17
Summary:
Expires:
Sender:
Followup-To:
Keywords:

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