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/15
Message-ID: <dewar.882235092@merv>#1/1
X-Deja-AN: 298546028
References: <gwinn-0812971210080001@dh5055133.res.ray.com>
 <EKxx9n.Ly1.0.-s@inmet.camb.inmet.com>
 <gwinn-1212971925480001@dh5055236.res.ray.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 882235266 2773 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-12-15T00:00:00+00:00
List-Id: <comp.lang.ada>


Joe says

<<I guess I would have to agree, because it's certainly too expensive for
realtime use.  We will invent some such solution as you suggest.
>>


No, that's wrong. If you do nothing but assignments and comparisons, there
is no overhead in the use of enumeration types with holes. If you index
compact arrays, or worse, do Succ or Pred, then you should have an
implementation model which tells you immediately that there is extra
overhead. This should not be a mystery.

Similarly, how could you possibly be surprised that x'Image(a) causes
a formatted conversion, THAT IS WHAT IMAGE IS ABOUT. There is no resaon
to forbid this. If you need the function of Image, you should use it, if
not you should not. I must say I find the comment on Image *very* odd!