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: bobduff@world.std.com (Robert A Duff) Subject: Re: Equality operator overloading in ADA 83 Date: 1997/04/24 Message-ID: #1/1 X-Deja-AN: 237115784 References: <01bc4e9b$ac0e7fa0$72041dc2@lightning> <335CAEFE.35DC@elca-matrix.ch> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada Date: 1997-04-24T00:00:00+00:00 List-Id: In article , Robert Dewar wrote: >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. There is an AI, and I posted it in another note. The ARG made a "final" decision, but WG9 has not yet voted on it. My memory is that we discussed it at the Vermont meeting last Fall (I believe you were there, since you hosted the meeting ;-) ) and the entire ARG agreed unanimously that "=" should compose properly for all predefined types except System.Address. For System.Address, all but one ARG member agreed that "=" should compose -- I was the "one", and I argued that Address semantics are by their nature implementation dependent, so we shouldn't say anything about it. I was outvoted on that point. So, yes, you ought to change Bounded_String to be tagged, or else use some special hack. Unless of course you think WG9 will disapprove the AI -- I doubt it. I also remember you saying that such special hacks are easy to implement in GNAT, so you could save one word per Bounded_String, if you like. - Bob