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: 19 Sep 92 02:31:59 GMT
From: seas.gwu.edu!mfeldman@uunet.uu.net  (Michael Feldman)
Subject: Re: Enumerations
Message-ID: <1992Sep19.023159.11763@seas.gwu.edu>
List-Id: <comp.lang.ada>

In article <1992Sep19.011823.15070@wdl.loral.com> mab@wdl39.wdl.loral.com (Mark
 A Biggar) writes:
>
>It was suggested early in the Ada9X effort that there should be attributes
>like 'POS and 'VAL that delt with the real stored values of enumerations.
>These were dropped as part of the Zero-budget simplifications.
>All I ment by relief was that Ada9x did not provide a more convienent method
>of dealing with the stroed values of enumeration literals then that provided
>by Ada83.
>
But I'm still puzzled. Why do you need to do this? Either you care about
the values, or you don't (depends on the application). If you don't care,
you treat the enumeration as purely abstract. If you _do_ care, you 
write a repspec, _then_ you treat the enumeration as abstract. Am I
missing something? Under what circumstances do you need to deal
directly with the stored values?

Mike Feldman