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,103b407e8b68350b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-01-09 05:34:50 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!sjc70.webusenet.com!news.webusenet.com!newsfeed2.earthlink.net!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!stamper.news.atl.earthlink.net!harp.news.atl.earthlink.net!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Anybody in US using ADA ? New language competition? (long) Date: Thu, 9 Jan 2003 08:34:30 -0500 Organization: MindSpring Enterprises Message-ID: References: <3E148004.5000408@cogeco.ca> <3E15CF31.1020900@cogeco.ca> <3E19C980.6060902@cogeco.ca> NNTP-Posting-Host: d1.56.b8.8f X-Server-Date: 9 Jan 2003 13:34:50 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Xref: archiver1.google.com comp.lang.ada:32819 Date: 2003-01-09T13:34:50+00:00 List-Id: I'd agree that you wouldn't want to try to get it to work on either only 1 compiler or on all compilers. Its not useful unless it really is portable to some extent and obviously, not all compilers would be appropriate. (Would an embedded compiler be able to utilize a GUI?) You'd have to pick a set of compilers (and volunteers) who would (dare I use the word?) "Validate" that the toolset worked in that environment. No small job, but I'd expect that it wouldn't have to be *perfect* (bug-free) - just compilable and executable for some major functionality. A bit more than a smoke test and significantly less than a formal qualification test. "Vendor Neutral" might be a bit harder. For some things (like a database?) it would probably work, but for others (like a GUI?) it might be competing against what a vendor already has. If you work to the least common denominator (things that no vendor will object to as a competing product) you probably will have a very small library. Not sure how to handle that one other than to have SIGAda distribute a disk full of stuff and if it gains acceptance as "Conventional Ada" then the vendors will ultimately have to follow. MDC -- ====================================================================== Marin David Condic I work for: http://www.belcan.com/ My project is: http://www.jast.mil/ Send Replies To: m c o n d i c @ a c m . o r g "I'd trade it all for just a little more" -- Charles Montgomery Burns, [4F10] ====================================================================== Randy Brukardt wrote in message news:v1p2fu1h297j04@corp.supernews.com... > > I'm sure the vendors are in favor of someone doing that. But it will > need to be vendor-neutral -- it does no good if most of the code only > compiles with GNAT. Then vendors will say -- yet another hobbyest > library for GNAT -- and ignore it. > > I'll reiterate that our experience with Claw is that GNAT is no better > or worse than other Ada compilers for bugs. It allows some illegal code, > won't compile some legal code, etc. In order to have something useful to > end users, it really has to be the case that you can pick up the > packages off of the SigAda web site and use them, no matter what Ada > compiler you are using. For that to be the case, they have to have been > compiled successfully with at least 3 different Ada compilers. > > Of course, some compilers may be just too buggy or limited to work with > some software. I suspect just making the code work on GNAT, ObjectAda, > and Rational Apex would be enough. You may not want to be restricted to > the least common denominator code (like we did with Claw). > > Anyway, RRS would distribute such a library if it made sense, and making > it work did not take up too many resources. After all, given: > 10 bugs reported by customers; > 10 bugs in new ACATS tests; and > 10 bugs in a pseudo-standard library > it's fairly likely that work on the library will be later in the list. > :-) > > Randy Brukardt > > >