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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,967a201c4428b348 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-01-01 17:17:09 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!sn-xit-01!sn-xit-09!supernews.com!204.127.198.204.MISMATCH!attbi_feed4!attbi.com!attbi_s01.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Enumeration representation References: X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 67.161.24.134 X-Complaints-To: abuse@comcast.net X-Trace: attbi_s01 1073006228 67.161.24.134 (Fri, 02 Jan 2004 01:17:08 GMT) NNTP-Posting-Date: Fri, 02 Jan 2004 01:17:08 GMT Organization: Comcast Online Date: Fri, 02 Jan 2004 01:17:08 GMT Xref: archiver1.google.com comp.lang.ada:4028 Date: 2004-01-02T01:17:08+00:00 List-Id: > Having to define every enumeration twice could be a pain. You only need a rep clause if you want oddball values for the representations, ie, you are dealing with communication with a hardware device or another program and must adapt to its conventions. If you are just using the enumeration internally you don't care how the compiler represents it.