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,15267b2c375b45c2 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-10-22 04:14:35 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.mathworks.com!wn13feed!wn11feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc02.POSTED!not-for-mail From: "Jeff C," Newsgroups: comp.lang.ada References: <3F92BEAA.9030004@comcast.net> Subject: Re: Ada Component Registry proposal X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: NNTP-Posting-Host: 66.31.4.164 X-Complaints-To: abuse@comcast.net X-Trace: sccrnsc02 1066821274 66.31.4.164 (Wed, 22 Oct 2003 11:14:34 GMT) NNTP-Posting-Date: Wed, 22 Oct 2003 11:14:34 GMT Organization: Comcast Online Date: Wed, 22 Oct 2003 11:14:34 GMT Xref: archiver1.google.com comp.lang.ada:1399 Date: 2003-10-22T11:14:34+00:00 List-Id: "sk" wrote in message news:mailman.162.1066796252.25614.comp.lang.ada@ada-france.org... > "Robert I. Eachus" : > > What about Ada80.Sockets, Ada87.Sockets, and Ada2000.Sockets? > > > > The differences between some of these versions, and others not > > mentioned is slight. (For example, there were three differences > > between MIL-STD ... > > Interesting, I must look at my LRM (after I find it) to see whether I > followed MIL-STD or ANSI/MIL-STD Ada'83 :-) This also might explain a > recent problem of ARM quoting where myself and another where quoting > from the same textual section/paragraph but were using different chapter > numbers. However, I don't see this as particularly limiting. > > Another reason I would prefer a short and complete name, such as Ada95 > is that "CAL", "SAL", "XAL", "EACHUS" etc. don't suggest what they are > and they are acronyms or peoples personal labels rather than being > descriptive etc. > > > I'm not trying to be a stickler for accuracy here, just pointing out > > that the Ada standard is evolving. I'd hate to have the CAL come out > > labelled as Ada95 (or Ada2000) just in time for the Ada 0X standard. > > Yes, but the inventory would be for *now* which is for Ada95 and prior, > when sub-packages become suitable for Ada0x, then they move to the Ada0x > tree. Not picking, just do not see the difficulty. I think this is not the right path. When Ada 2020 comes out and we want to add a new subprogram to Ada05.Directory_Operations does that mean we now have an Ada20.Directory_Operations that looks the same but with the new procedure or do we add to it. No matter what the answer is I don't think I like it.