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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7ee10ec601726fbf X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-30 08:42:41 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!psinet-eu-nl!psiuk-p4!psiuk-p3!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: why not Date: Tue, 30 Oct 2001 10:35:04 -0500 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9rmhb9$o1b$1@nh.pace.co.uk> References: <3BC5D730.DA950CC7@boeing.com> <9q4pa7$1ad$1@nh.pace.co.uk> <3BC6ACC8.23EF21BC@free.fr> <3BC71F54.1FFE78FA@boeing.com> <1KGx7.26476$ev2.35117@www.newsranger.com> <3BC7AD82.2A0CCCD4@acm.org> <9qhiqr$af0$1@nh.pace.co.uk> <1nDC7.180$6S7.92255364@newssvr11.news.prodigy.com> <9rjsak$bp3$1@nh.pace.co.uk> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1004456105 24619 136.170.200.133 (30 Oct 2001 15:35:05 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 30 Oct 2001 15:35:05 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:15419 Date: 2001-10-30T15:35:05+00:00 List-Id: Well, that creates a clue as to how it might get done in Ada. However, I've heard here in the past objections from compiler vendors to adding this sort of library to the ARM as a part of the standard. Part of the problem is specifying the behavior in sufficient detail to make it verifiable. There is also a certain amount of inflexibility once it gets into the standard. I suppose some library could be identified and submitted to the appropriate keepers-of-the-standard, but that would obviously require a long time before it ever got in there. I'd think it would be easier if a few vendors were to state their willingness to adopt some TBD library that met some TBD minimal requirements and then let an informal committee (under SIGAda?) identify or develop something that met those requirements. Keep it simple & minimal so that it constitutes A Good Start & the vendors are free to accept/reject it for any reasons they like. Would the Ada community prefer to see it as a part of the ARM and wait until Ada0x for it to be realized? Would the Ada0x committee be willing to consider it? I would opt for something informal at first and see if it had sufficient utility to earn a place in the standard. There's a lot less risk that way. MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/ "Barry Kelly" wrote in message news:jbfstt097fvrrqmrl0kuscmbl57neg8imf@4ax.com... > > Stepanov wrote a generic library (initially in Ada 83, IIRC), then > wrote a new one for C++. Somebody (I can't remember who exactly) asked > if he'd considered trying to get it accepted as a standard library > addition proposal. It was late in the standardization cycle; he got > support of many of the key members, and he rewrote the documentation > to get it up to standardese standard, as it were. > > The story is someplace on the net; doubtless a little searching will > turn it up. >