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,8ffd9ca0013db6a7 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2000-11-02 07:03:10 PST Path: supernews.google.com!sn-xit-02!supernews.com!isdnet!209.249.123.233.MISMATCH!xfer10.netnews.com!netnews.com!cpk-news-hub1.bbnplanet.com!cambridge1-snf1.gtei.net!news.gtei.net!inmet!not-for-mail From: Tucker Taft Newsgroups: comp.lang.ada Subject: Re: Redefined "=" = generic disaster? Date: Thu, 02 Nov 2000 09:59:38 -0500 Organization: AverStar (formerly Intermetrics) Burlington, MA USA Message-ID: <3A01815A.75D30E9F@averstar.com> References: <39F13ED9.1EE@li.net> <39F1C092.87D4135E@acm.org> <39F1F686.26B5@li.net> <8tecab$epm$1@nnrp1.deja.com> <39FCEFAD.56BE85B1@ix.netcom.com> <8tkfme$v8a$1@nnrp1.deja.com> <39FE3C35.64CBB3C7@ix.netcom.com> <8tn7s1$9gp$1@nnrp1.deja.com> <3A005722.7E0BC50@mail.com> NNTP-Posting-Host: nebula.burl.averstar.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: inmet2.burl.averstar.com 973177178 17691 141.199.8.77 (2 Nov 2000 14:59:38 GMT) X-Complaints-To: usenet@inmet2.burl.averstar.com NNTP-Posting-Date: 2 Nov 2000 14:59:38 GMT X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en Xref: supernews.google.com comp.lang.ada:1721 Date: 2000-11-02T14:59:38+00:00 List-Id: Mats Weber wrote: > > Robert Dewar wrote: > > > [...] > > I still don't get it, the original claim was that there was > > something special about "=" that made things particularly > > awkward. > > [...] > > I first wanted to shut up on this issue when I saw it reemerge. But I > can't tell people to go to deja.com and search for it because searches > for postings prior to May 15, 1999, are temporarily unavailable. > > I think there really is a problem with the reemergence of predefined > operations within generics, and that problem has been acknowleged by the > Ada 95 design team: draft versions of the 9X reference manual had rules > removing the reemergence problem, but later these rules were removed in > the final Ada 95 RM. IMO, this was a mistake. My current thinking is that we should have preserved the Ada 83 reemergence rules for everything except record types. Record types are the primary way to implement private types, which is what really matters. Furthermore, because a record type might contain a tagged type with a user-defined "=", the generic instantion mechanism needs to be prepared to handle user-defined code as part of even the predefined record "=". On the other hand, it could be a real implementation burden to make a generic instantiation substitute a user-defined operator for scalar or access types. Bob Duff and I used to say "tagged types work right" with respect to generics. It might be nice to generalize that to "record types work right." As part of this generalization, it would be nice if formal derived types would also work "right" for record types. To minimize incompatibilities, this would probably require that if a type were passed to a generic formal derived untagged record type (that's a mouthful ;-), it would need for all of its primitive operations to be mode conformant with the corresponding operations of the specified ancestor type. This is a pretty mild requirement, of course. > ... -Tucker Taft -- -Tucker Taft stt@averstar.com http://www.averstar.com/~stt/ Technical Director, Commercial Division, AverStar (formerly Intermetrics) (http://www.averstar.com/services/IT_consulting.html) Burlington, MA USA