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,cda33fc7f63c2885 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-01-19 14:51:06 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!fu-berlin.de!uni-berlin.de!ppp-1-114.cvx1.telinco.NET!not-for-mail From: "Nick Roberts" Newsgroups: comp.lang.ada Subject: Re: Overridability of _private_ predefined "=" [was Re: list strawman] Date: Sat, 19 Jan 2002 22:42:29 -0000 Message-ID: References: <6i%_7.8890$fG.50588@rwcrnsc51.ops.asp.att.net> <3C47E79E.7844@li.net> <3C49A5C4.51D6@li.net> NNTP-Posting-Host: ppp-1-114.cvx1.telinco.net (212.1.136.114) X-Trace: fu-berlin.de 1011480665 33125351 212.1.136.114 (16 [25716]) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Xref: archiver1.google.com comp.lang.ada:19108 Date: 2002-01-19T22:42:29+00:00 List-Id: "Vincent Marciante" wrote in message news:3C49A5C4.51D6@li.net... > ... > This is why I find the situation to be so bad now. A generic written > for Ada 83 that only imports a private type can not be made into a valid > Ada 95 one by simply transforming its spec by adding the importation of > "=" for that type; Its body must also be analyzed and possibly changed > so as to use componant by componant comparison for any composite types > having the private type as a componant (or predefined "=" has to be > overridden for those composite types _and_ any other composite types the > have those composite types as componants.) > > What was impossible (?) to do wrong in Ada 83 has now become a pitfall > in Ada 95. were by we have to dilligently follow the verbal guideline > that you just suggested. AI-123 discusses this in some detail, and results (rev 12) in a corrigendum which specifically compels language-defined types to be composable with respect to equality (thus forcing them to be implemented either without redefined equality or as tagged types). I smell a hint of hypocrisy here. Personally, I completely agree with Vincent. Damn Ada 83 compatibility, and damn implementation complexities: equality should always be composable; the current state is plainly a potential source of 'nasty surprises'; the language is purportedly supposed to avoid nasty surprises. But I am a small voice. -- Best wishes, Nick Roberts