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: Simon Wright Subject: Re: Equality operator overloading in ADA 83 Date: 1997/04/28 Message-ID: #1/1 X-Deja-AN: 238017542 X-NNTP-Posting-Host: pogner.demon.co.uk References: <01bc4e9b$ac0e7fa0$72041dc2@lightning> <01bc5244$315f1560$28f982c1@xhv46.dial.pipex.com> Organization: At Home Newsgroups: comp.lang.ada Date: 1997-04-28T00:00:00+00:00 List-Id: 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 ... > In a way this happens in the Xt (Motif) arrangement for resource names: the effect is somewhat like having an associative array. I guess if that was the requirement, and the index names were predetermined, you might want to do it using a case ... I don't suppose Xt is very clever here, there is some optimisation to allow the use of predeclared instances of the strings so that an address comparison can be used instead of strcmp().