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.1 required=5.0 tests=BAYES_20,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!wuarchive!mit-eddie!bu.edu!inmet!stt
From: stt@inmet.inmet.com
Newsgroups: comp.lang.ada
Subject: Re: Keyword reuse.
Message-ID: <20600055@inmet>
Date: 5 Jul 90 20:21:00 GMT
References: <57965@bbn.BBN.COM>
Nf-ID: #R:bbn.BBN.COM:57965:inmet:20600055:000:670
Nf-From: inmet.inmet.com!stt    Jul  5 16:21:00 1990
List-Id: <comp.lang.ada>


Re: reuse of keywords

There *is* a cost to adding reserved words.  The ones
I "run" into most often are "entry" and "select," where
I am minding my own business writing a simple queueing package,
or a simple menu package, and suddenly a bolt of lightning
out of the tasking side of Ada hits me and my identifiers
get declared RESERVED FOR MULTITASKING.

In any case, what in one person's view is "inappropriate reuse"
in another person's view is "appropriate overloading."
"Raise;" seems like an appropriate overloading to me,
but of course, I have read the "green book" so many times
that I dream in Ada... :-}

S. Tucker Taft
Intermetrics, Inc.
Cambridge, MA  02138