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, LOTS_OF_MONEY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,842accb6a7d76669 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-09 09:50:13 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: List container strawman 1.1 Date: Fri, 9 Nov 2001 12:37:58 -0500 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9sh49o$ohc$1@nh.pace.co.uk> References: <3BE301D1.4010106@telepath.com> <3BE7DA00.8020807@acm.org> <9sdojl$e6h$1@news.huji.ac.il> <3BEACA5A.9030100@acm.org> <20TG7.18929$xS6.30469@www.newsranger.com> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1005327480 25132 136.170.200.133 (9 Nov 2001 17:38:00 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 9 Nov 2001 17:38:00 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:16148 Date: 2001-11-09T17:38:00+00:00 List-Id: I'm wondering if everyone is declaring it "Unacceptable" or perhaps a little less strongly, it is merely being viewed as "Undesirable". (That would describe my gut feeling on it.) I'd still think that the BC's might be usable if some conditions were met. 1) See if you can hide some of the complexity by making a simple-case binding for the most common usages. 2) Create a "Booch Components for Idiots" text that shows cookie-cutter recepies for how to do the simple cases (covers up for #1 if that's not feasable.) 3) Get some reasonable level of concensus that the BC's are an acceptable, if not perfect, solution. (I'd agree to this - how about the rest of the crowd?) Or it might be possible to declare as part of the BC's++ that there will be a couple of new packages that handle the simple cases while keeping the rest of the BC's around for the more advanced user? I think the biggest problem here is that we all have our own particular desires, programming styles, knowledge-base, etc., that keeps us hoping we can get something more to our liking. Nothing wrong with that, but the likely outcome of insisting on it is going to be that everyone goes their own way and we're right back here at the beginning with no common component library. Is it possible we might work in this direction: 1) Accept the BC's as a working hypothesis. 2) Extend the BC's to include some List and Map components that handle the simple cases without too much pain. (Basically, something like what Ted put out as a strawman. It either stands alone or is implemented with the BC's as a wrapper around them.) 3) Add on to the BC's the capability of loading and storing the components to files via some version of working nicely with Streams. 4) Come up with a document that does a little bit of basic "How To" explaining and have this go along for the ride in some way. 5) Get some acceptance from the vendors to have this endorsed and hopefully shipped with some compilers. What I'm outlining above doesn't sound like it is impossible to accept nor does it constitute some astronomical level of work. A small group of us might be able to accomplish this before the next ice age. Would this be acceptable to anyone? 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/ "Ted Dennison" wrote in message news:20TG7.18929$xS6.30469@www.newsranger.com... > instantiation of it) to instantiate the second package. Its not too horrible one > you figure it out. But this is exactly what Booch does that everyone is saying > is unacceptable. So I feel that we really need to avoid using child packages > unless there is a compelling reason. >