From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 30 Jun 93 23:06:18 GMT
From: eachus@mitre-bedford.arpa  (Robert I. Eachus)
Subject: Re: Ada Operators in 9x
Message-ID: <EACHUS.93Jun30180618@spectre.mitre.org>
List-Id: <comp.lang.ada>

In article <1993Jun30.174116.24785@relay.nswc.navy.mil> bwallet@apssgi.nswc.nav
y.mil (Brad Wallet) writes:

  > no, i think you all are missing point behind making Ada case sensitive.
  > since the original statement was that case sensitivity would allow for
  > more uniform coding standards enforcement by the language, i think the
  > implementation would be something like all reserved words must be
  > written in lower case and other stuff must be all caps.  that's part of
  > our coding standards.  this would make perfect sense...

  Gee, since you are too lazy (apparently) to build a tool to enforce
your coding standards on everyone in the project, you want to require
all Ada compilers to enforce them on everyone!  That DOES NOT make
perfect sense to me.

     A long time ago a group I was in built a (very nice) pretty
printer for Ada for the project we were doing.  After lots of rounds
of discussions directed at which format was best, we compromised on
everybodies favorites.  Emacs ada-mode was modified to run files
through the pretty printer using the individual preferences when
loading, compiling, or saving, and a print alias used a separate set
of preferences for printing source files.  (For example, I prefer two
or three space indentation on screens, five spaces on wide printouts.)

     This worked just fine.  The only refinement added later was to
have a set of "project" preferences for delivered code.
--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...