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: Samuel Tardieu Subject: Re: Beware: Rep spec on an enumeration type causes code explosion Date: 1997/12/12 Message-ID: #1/1 X-Deja-AN: 297549313 References: <66po35$1a1$1@gte2.gte.net> Mail-Copies-To: sam@ada.eu.org To: mheaney@ni.net (Matthew Heaney) Organization: TELECOM Paris Newsgroups: comp.lang.ada Date: 1997-12-12T00:00:00+00:00 List-Id: Matthew> If you are using a holey type inside the application, ie not Matthew> at the interface layer only, then you are probably doing Matthew> something wrong. The fact that you're using your own Boolean Matthew> type does not bode well! This kind of code is horrible as he admits, but I don't think it is wrong; they just consider the RAM as being an external device, thus using a holey boolean type. When they compare their own booleans to True_State and False_State, the result is likely to be stored in a register only and never in RAM, and registers are probably considered as "safe". Sam -- Samuel Tardieu -- sam@ada.eu.org