Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!aglew From: aglew@crhc.uiuc.edu (Andy Glew) Newsgroups: comp.lang.c Subject: Re: Coding Standards. was: a style question Message-ID: Date: 29 Nov 90 21:17:55 GMT References: <1990Oct23.160116.10299@athena.mit.edu> <13@christmas.UUCP> <14369@smoke.brl.mil> <1990Nov10.191840.21113@clear.com> <7267@hub.ucsb.edu> <6733@uceng.UC.EDU> <1990Nov18.005030.28841@zoo.toronto.edu> <6741@uceng.UC.EDU> <17673@thorin.cs.unc.edu> Sender: news@ux1.cso.uiuc.edu (News) Organization: Center for Reliable and High-Performance Computing University of Illinois at Urbana Champaign Lines: 18 In-Reply-To: leech@homer.cs.unc.edu's message of 19 Nov 90 20:56:27 GMT >Since these two programmers disagree about a detail which is easy >to embed in a beautifier program, since it depends only on syntax, >then a beautifier program should be able to mediate the style >disagreement, and allow each programmer to view the other's code >consistently with personal preference. Interesting consequences for revision control systems may arise with such an approach. -- Jon Leech (leech@cs.unc.edu) __@/ Why? If all program text can be massaged by the beautifier, run all text through the beautifier to some "standard" setting before checking in. -- Andy Glew, a-glew@uiuc.edu [get ph nameserver from uxc.cso.uiuc.edu:net/qi]