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,38fc011071df5a27 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-09-18 09:37:47 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!news.uunet.ca!nf3.bellglobal.com!nf1.bellglobal.com!nf2.bellglobal.com!news20.bellglobal.com.POSTED!not-for-mail From: "Warren W. Gay VE3WWG" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: How to get a =?ISO-8859-1?Q?=BBConventional_Ada_Library=AB?= =?ISO-8859-1?Q?_=28Was=3A_Ideas_for_Ada_200X=29?= References: <6a90b886.0305262344.1d558079@posting.google.com> <3ED4A94C.2020501@noplace.com> <3ED6A852.75AC0133@adaworks.com> <3ED74ED3.4020505@noplace.com> <3ED7C8C5.3070902@cogeco.ca> <3ED826BB.9010509@noplace.com> <3F61BA28.3060507@crs4.it> <3F6205B8.3070402@attbi.com> <3F6316DC.7080106@noplace.com> In-Reply-To: <3F6316DC.7080106@noplace.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Date: Thu, 18 Sep 2003 12:22:50 -0400 NNTP-Posting-Host: 198.96.223.163 X-Complaints-To: abuse@sympatico.ca X-Trace: news20.bellglobal.com 1063902156 198.96.223.163 (Thu, 18 Sep 2003 12:22:36 EDT) NNTP-Posting-Date: Thu, 18 Sep 2003 12:22:36 EDT Organization: Bell Sympatico Xref: archiver1.google.com comp.lang.ada:42659 Date: 2003-09-18T12:22:50-04:00 List-Id: Marin David Condic wrote: ... > As for a conventional Ada library getting too complex, let me start > here: To the extent that containers are part of such a library, I'd > support a plain-vanilla set of lists and maps with "Ease Of Use" as a > primary goal. I'd also want to consider a second set of more elaborate > and powerful containers with "Maximum Utility" as a goal - on which you > go build whatever else you want to stick into the library. Make sure it > is well documented. I would support this idea. > Second, as for any concerns about "largeness" or "complexity" - lets do > a counter-proof by existence: Java has a really large library. So does > MSVC++. Programmers use those libraries *every*day* to build systems. If > they count as "large" and "complex", then this must not be a handicap. > If they are not "large" or "complex" then let's go off and build > something similar to what they have and call that a Conventional Ada > Library and we would similarly not be "large" and "complex". I think this is an excellent point that you make here. How many times have we heard that a such-n-such proposal/implementation is too large or complex, and then stop there. Yet, as you point out, others are already _using_ libraries far more (or equally) complex in their day to day work. Simplicity is certainly a good goal, but let's all realize that sometimes functionality dictates a more complicated world. Equally important is the fact that "they" are using something, and often "we" are not. While the Booch Components often gets criticised for their complexity (in instantiation mostly I think), they are a very functional set of packages. They would be easier to use with the appropriate level of documentation, which hasn't happened yet (I had actually made it a goal to write such, but as you can see, haven't come through on that yet). But the point here is that they are fairly complete in functionality, but yet for one reason or another, not fully accepted by the community (or maybe they have, but the lurkers are not saying that ;-) ). > MDC -- Warren W. Gay VE3WWG http://home.cogeco.ca/~ve3wwg