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.1 required=5.0 tests=BAYES_00,PDS_OTHER_BAD_TLD autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a644fa9cd1a3869a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-15 17:59:22 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!newsfeed1.earthlink.net!newsfeed.earthlink.net!newsmaster1.prod.itd.earthlink.net!newsread1.prod.itd.earthlink.net.POSTED!not-for-mail Message-ID: <3BF472EF.FE3F2FF@acm.org> From: Jeffrey Carter X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: List container: Sawdust woman 43 References: <9sn4qm$13g29j$2@ID-25716.news.dfncis.de> <3BF140D9.611DE43@brighton.ac.uk> <9srvmk$1la$1@news.huji.ac.il> <3BF2699A.731DC436@brighton.ac.uk> <9su77k$c83$1@news.huji.ac.il> <9sucit$qde$1@nh.pace.co.uk> <3BF344AD.42FCB303@acm.org> <9t0mq2$1u6$1@nh.pace.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 16 Nov 2001 01:59:17 GMT NNTP-Posting-Host: 158.252.147.47 X-Complaints-To: abuse@earthlink.net X-Trace: newsread1.prod.itd.earthlink.net 1005875957 158.252.147.47 (Thu, 15 Nov 2001 17:59:17 PST) NNTP-Posting-Date: Thu, 15 Nov 2001 17:59:17 PST Organization: EarthLink Inc. -- http://www.EarthLink.net X-Received-Date: Thu, 15 Nov 2001 17:55:12 PST (newsmaster1.prod.itd.earthlink.net) Xref: archiver1.google.com comp.lang.ada:16607 Date: 2001-11-16T01:59:17+00:00 List-Id: Marin David Condic wrote: > > Maybe you misinterpreted what I was suggesting. Hypothetically, the decision > could be taken to make PragmARC the "Standard Component Library" (Not > necessarily part of the ARM...) - but given some of the requirements, there > would need to be some enhancements made. (It doesn't support getting lists, > etc into Streams?) If the community was willing to buy into that concept and > we could identify a desired set of extensions/enhancements to make PragmARC > more acceptable to the community, would that adaptation be something you'd > be willing to supervise/coordinate? Maybe I did. I certainly would have no objection if the Ada community chose to adopt the PragmARCs as a standard library, and would be willing to help incorporate enhancements that had a consensus as needed. I was under the impression that the PragmARC's list component, at least, was widely considered unacceptable for such a library because of some of the design decisions. I would still not expect the PragmAda name to be connected to the library after acceptance as a standard library, since it would be the specifications that were accepted, and other implementations may be provided, as with the Ada.XYZ packages. In the meantime, I'll hold my breath while waiting for you to form a consensus for adopting an existing library. While I'm turning blue, it might still be nice to get people's comments on how the PragmARC list specification would have to change to be acceptable. -- Jeffrey R. Carter PragmAda Software Engineering