Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!pyrltd!root44!praxis!mikec
From: mikec@praxis.co.uk (Michael Chace)
Newsgroups: comp.software-eng
Subject: Re: Automated tools for verifying C style compliance?
Message-ID: <MIKEC.90Nov21074817@hilbert.praxis.co.uk>
Date: 21 Nov 90 07:48:17 GMT
References: <4990@tekfdi.FDI.TEK.COM> <5815@stpstn.UUCP>
Sender: mikec@praxis.co.uk
Organization: PraXis Systems plc, Bath, Avon UK
Lines: 24
In-reply-to: cox@stpstn.UUCP's message of 17 Nov 90 18:23:16 GMT
X-Mailer: GNU Emacs VM

>>>>> Regarding Re: Automated tools for verifying C style compliance?; cox@stpstn.UUCP (Brad Cox) adds:

Brad> In article <4990@tekfdi.FDI.TEK.COM> kyleb@tekfdi.FDI.TEK.COM (Kyle Bernard) writes:
>I've recently read over the C style guidelines from giza.cis.ohio-state.edu
>(128.146.8.61) and it seems their usefulness is very limited due to the lack
>of automated compliance verficiation tools.

Brad> Why bother with compliance checking tools. Wouldn't the same effort be
Brad> spent more productively on a pretty-printer that reformat source to whatever
Brad> formatting standard you prefer, and let people write as they wish?

Why not do better from scratch by using a decent editor (ie emacs) that has
an adequate mode for editing C source files ?

Mike
****
.............................................................................
|                                                | Michael Chace            |
| e-mail   :  mikec@praxis.co.uk                 | PraXis Systems           |
|                                                | Manvers Street           |
| AMPRNET:  g6dhu@g6dhu.ampr.org   [44.131.20.3] | Bath,  Avon              |
| AX.25  :  G6DHU @ G6DHU-2 or G6DHU @ GB7SDN    | BA1 1PX           UK     |
| Phone  :  (44) [0]225 444700                   |                          |
.............................................................................