From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,15890893c0618a8a
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: [Q] Tools for Ada Quality and Style
Date: 1996/04/28
Message-ID: <dewar.830719362@schonberg>#1/1
X-Deja-AN: 151920071
references: <9604172134.AA27114@eight-ball> <767968529wnr@diphi.demon.co.uk>
 <4ltjat$dao@parlor.hiwaay.net>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-04-28T00:00:00+00:00
List-Id: <comp.lang.ada>


Bob Crispen was looking for pretty printing tools to enforce a standard.

I must say I do not like this approach. For uniform style rules to work,
everyone has to buy into them, and buying into them means getting 
completely familiar with them and not considering writing code in any
other style. 

If you rely on pretty printing tools, then there is a danger of continuing
to foster a sloppy attitude to the style rules.

I *do* like tools that enforce style rules, to the extent that this is
possible. Many style rules are simply too indefinite to enforce
mechanically.