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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,a50a3c40267219cc
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-10-23 17:03:42 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!fr.usenet-edu.net!usenet-edu.net!enst!enst.fr!not-for-mail
From: "Beard, Frank" <beardf@spawar.navy.mil>
Newsgroups: comp.lang.ada
Subject: RE: Why not combine Ada and C++?
Date: Tue, 23 Oct 2001 20:02:08 -0400
Organization: ENST, France
Sender: comp.lang.ada-admin@ada.eu.org
Message-ID: <mailman.1003881820.5181.comp.lang.ada@ada.eu.org>
Reply-To: comp.lang.ada@ada.eu.org
NNTP-Posting-Host: marvin.enst.fr
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Trace: avanie.enst.fr 1003881821 12860 137.194.161.2 (24 Oct 2001 00:03:41
 GMT)
X-Complaints-To: usenet@enst.fr
NNTP-Posting-Date: Wed, 24 Oct 2001 00:03:41 +0000 (UTC)
To: "'comp.lang.ada@ada.eu.org'" <comp.lang.ada@ada.eu.org>
Return-Path: <beardf@spawar.navy.mil>
X-Mailer: Internet Mail Service (5.5.2448.0)
Errors-To: comp.lang.ada-admin@ada.eu.org
X-BeenThere: comp.lang.ada@ada.eu.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:comp.lang.ada-request@ada.eu.org?subject=help>
List-Post: <mailto:comp.lang.ada@ada.eu.org>
List-Subscribe: <http://ada.eu.org/mailman/listinfo/comp.lang.ada>,
	<mailto:comp.lang.ada-request@ada.eu.org?subject=subscribe>
List-Id: comp.lang.ada mail<->news gateway <comp.lang.ada.ada.eu.org>
List-Unsubscribe: <http://ada.eu.org/mailman/listinfo/comp.lang.ada>,
	<mailto:comp.lang.ada-request@ada.eu.org?subject=unsubscribe>
List-Archive: <http://ada.eu.org/pipermail/comp.lang.ada/>
Errors-To: comp.lang.ada-admin@ada.eu.org
X-BeenThere: comp.lang.ada@ada.eu.org
Xref: archiver1.google.com comp.lang.ada:15108
Date: 2001-10-23T20:02:08-04:00

-----Original Message-----
From: Kilgallen@SpamCop.net [mailto:Kilgallen@SpamCop.net]

>> However, as a minor exception to that, we do use all uppercase to
>> indicate constants, as in MAXIMUM_DEVICES.

> That must make for a lot of editing when a former constant becomes
> a variable or a function call in some subsequent version.

It hasn't happened yet, but you're right, it could be a problem if
you haphazardly pick names that you might intermix as constants or
variables.  We tend to use names containing the word MAXIMUM, MINIMUM,
LIMIT, etc., for constants.  As far as changing constants to functions,
most of our constants are in the package bodies, and exported through
functions.

It was a Style Guide/Coding Standards decision made 8 years ago for
the various projects.  It hasn't come back to haunt us yet.