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: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Equality operator overloading in ADA 83 Date: 1997/04/24 Message-ID: #1/1 X-Deja-AN: 237017449 References: <01bc4e9b$ac0e7fa0$72041dc2@lightning> <335CAEFE.35DC@elca-matrix.ch> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-04-24T00:00:00+00:00 List-Id: <<> You the purchaser of a compiler should test to make sure Bounded_String > works. If the predefined equality is ever getting called, let your vendor > know his product is broken. Perhaps this should be an ACVC test, too > (maybe it is already).>> Is this right, I do not know of an AI that has been issued that requires equality to compose on the Bounded_String type. Bob (Duff) isn't that right -- we discussed it, but made no final decision as I remember. GANT's behavior may note be what people want here, but I don't want to change it, and encourage people to write incorrect code that assumes that equality on bounded strings does compose, unless there is an AI that requires this. If there is an AI, please let me know (memory is not always trusty here :-)