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: 17 Sep 92 23:40:26 GMT
From: simonson@beaver.cs.washington.edu  (Kevin Simonson)
Subject: Re: Enumerations
Message-ID: <1992Sep17.234026.27654@beaver.cs.washington.edu>
List-Id: <comp.lang.ada>

     In article <1992Sep17.222636.4782@aio.jsc.nasa.gov>
davenpor@sweetpea.jsc.nasa.gov (Darren Davenport 283-4173) writes:

=In article <9209162110.AA21397@efftoo.boeing.com>, crispen@efftoo.boeing.com
=(crispen) writes:
...
=|> But what I'd like to know is, does anyone know of an Ada compiler
=|> which does not give a machine value of zero for the first element of
=|> an enumeration, one for the second, and so on?
=|> 
=|> Just idle curiosity, actually, since it came up in the context of a
=|> document I'm writing that's going to say, "Use rep specs for interface
=|> objects and don't trust different compilers to do the same thing".
...
=You do not need to write that in your document because:
=
="The position number of the value of the first listed enumeration literal is
=zero" LRM 3.5.1(4). 

     I was of the impression that the "position number" 3.5.1(4) referred
to was the value returned by the "'pos" attribute, and that that value
could be very different from the "machine value" that Crispen seems to be
talking about.  I'm not convinced we've found an answer to his question
yet.

                                     ---Kevin Simonson