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,c3a7c1845ec5caf9 X-Google-Attributes: gid103376,public From: eachus@spectre.mitre.org (Robert I. Eachus) Subject: Re: Equality operator overloading in ADA 83 Date: 1997/04/29 Message-ID: #1/1 X-Deja-AN: 238223622 References: <01bc4e9b$ac0e7fa0$72041dc2@lightning> <01bc5244$315f1560$28f982c1@xhv46.dial.pipex.com> Organization: The Mitre Corp., Bedford, MA. Newsgroups: comp.lang.ada Date: 1997-04-29T00:00:00+00:00 List-Id: In article Simon Wright writes: dewar@merv.cs.nyu.edu (Robert Dewar) writes: > it is simply > too unusual an idiom (a case against a large number of strings that are > staticaly known at compile time) to be worthwhile. I have trouble thinking > of any reasonable examples ... Another case that does come up is in parsing IFF formated files. Every section has a tag which is treated as an integer, but the tag values are selected to be meaningful. For example one image format used is ILBM (interleaved bit map). Now you can write: type IFF_TAG is (ILBM...); for IFF_TAG use (16#494C424D#,...); case Tag is when ILBM... But it sure would be nice not to have to worry that you declared all those tag values right. (And if I was doing a serious IFF parser, I would write a program to write that type declaration.) -- Robert I. Eachus with Standard_Disclaimer; use Standard_Disclaimer; function Message (Text: in Clever_Ideas) return Better_Ideas is...