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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,ca9eef4d5e2078ea
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Beware: Rep spec on an enumeration type causes code explosion
Date: 1997/12/14
Message-ID: <dewar.882158727@merv>#1/1
X-Deja-AN: 298258494
References: <gwinn-0812971210080001@dh5055133.res.ray.com>
 <EKxx9n.Ly1.0.-s@inmet.camb.inmet.com> <348F13DA.FC6@gsfc.nasa.gov>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 882158846 6952 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-12-14T00:00:00+00:00
List-Id: <comp.lang.ada>


Stephen says

<<I'm fairly sure that in most of the code I've written, if I supply a rep
clause for an enumeration type, I use it mainly as parameters to and
results from imported functions (Win32 comes to mind), but not as an
array index or with succ/pred. Often the results are used in case
statements. I guess this maps well to named private-type constants,
where the full type is simply an integer. However, it loses the
completeness check on case statements, which is always useful.
>>


Using case statements is reasonable, and should be reasonably efficient
if your compiler generally makes an effort to be reasonably efficient on
generting code for case statements. ertainly if the representation is
reasonbly compact (holes not too large), then the code should be efficient.