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,f70e76a7cef942c X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-30 09:36:11 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: C v C++ Date: Fri, 30 Nov 2001 12:01:18 -0500 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9u8e10$47s$1@nh.pace.co.uk> References: <3c075b22@pull.gecm.com> <9u851b$7d$1@nh.pace.co.uk> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1007139680 4348 136.170.200.133 (30 Nov 2001 17:01:20 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 30 Nov 2001 17:01:20 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:17231 Date: 2001-11-30T17:01:20+00:00 List-Id: Well its hard to blame a whole design method for every form of code bloat and yes, I agree that a lot of it has to do with bad design and poor management of a project. Still, with OOD there is some non-trivial overhead that goes with the implementation and the method itself leads to a kind of over-generalization that can make the code expand in size from what might be a more optimal solution. You get flexibility, ease of enhancement and reusability out of that sort of design, but you're paying for it by having the code increase in volume. I don't think OOD is the worst offender, but it certainly contributes. Its also not necessarily a problem that code may be more bloated than it absolutely has to be. Depends on what you're doing... 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/ "Pat Rogers" wrote in message news:JGNN7.872$ea1.327201861@newssvr30.news.prodigy.com... > > For poorly-done OOD, yes. Otherwise I do not find it inherent. There > certainly is the school of thought that absolutely every "class" must be > perfectly complete for every conceivable use, and for some things I buy that > and it could be a factor, but in general I do not. In the bad old days > there was no way to remove unused routines, so all the code in a package > would be included in the executable -- and that can certainly lead to > bloat -- but those days are gone. > > For my 2 cents code bloat is a result of poor design and poor management > (e.g. feature/requirements creep). > > > -- > --- > Patrick Rogers Consulting and Training in: > http://www.classwide.com Real-Time/OO Languages > progers@classwide.com Hard Deadline Schedulability Analysis > (281)648-3165 Software Fault Tolerance > >