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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC 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: Alan E & Carmel J Brain Subject: Re: Beware: Rep spec on an enumeration type causes code explosion Date: 1997/12/12 Message-ID: <34921C4D.4B0D@dynamite.com.au>#1/1 X-Deja-AN: 297517978 References: <348F3DFC.10DB@nospam.flash.net> <3490252D.6B550F17@ac3i.dseg.ti.com> Organization: @home Reply-To: aebrain@dynamite.com.au Newsgroups: comp.lang.ada Date: 1997-12-12T00:00:00+00:00 List-Id: John G. Volan wrote: > There is no need for anything so elaborate. Just derive a holey > enumeration type from a contiguous enumeration type. --->8--- > My feeling is that "holey" enumeration types (like other Chapter 13 > features) should really only be used at the "edges" of a program, --->8--- > Contiguous enumeration > types should be used internally everywhere else in your program Concur. Matches my own experience exactly. Although we didn't test to see what the performance hit would have been if we'd have used the rep type throughout. Any experimental data on this? -- aebrain@dynamite.com.au <> <> How doth the little Crocodile | Alan & Carmel Brain| xxxxx Improve his shining tail? | Canberra Australia | xxxxxHxHxxxxxx _MMMMMMMMM_MMMMMMMMM abrain@cs.adfa.oz.au o OO*O^^^^O*OO o oo oo oo oo By pulling MAERKLIN Wagons, in 1/220 Scale