Newsgroups: comp.lang.c++,comp.object,comp.theory,comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!portc01.blue.aol.com!portc02.blue.aol.com!cpk-news-hub1.bbnplanet.com!su-news-hub1.bbnplanet.com!news.bbnplanet.com!news.sgi.com!rutgers.rutgers.edu!utcsri!info.ecf!doylep
From: doylep@ecf.toronto.edu (Patrick Doyle)
Subject: Re: Opinions on Ellipse-Circle dilemma?
Sender: news@ecf.toronto.edu (News Administrator)
Message-ID: <E6Mo2t.F6w@ecf.toronto.edu>
Date: Thu, 6 Mar 1997 15:23:16 GMT
Distribution: inet
X-Nntp-Posting-Host: skule.ecf
References: <5d4fmf$7gk@bagan.srce.hr> <01bc2280$f02beca0$371883cc@beast.advancedsw.com> <rmartin-0403971738160001@pool11-000 <01bc2989$33a8f360$371883cc@beast.advancedsw.com>
Organization: University of Toronto, Engineering Computing Facility
Lines: 16
Xref: glinda.oz.cs.cmu.edu comp.lang.c++:251836 comp.object:61834 comp.theory:18280 comp.lang.smalltalk:52616

In article <01bc2989$33a8f360$371883cc@beast.advancedsw.com>,
Roger T. <roger@advancedsw.com> wrote:
>
>The performance increase in this instance is minimal as all an ellipse
>instance has to do is one check , (if a==b), to allow circle behavior, and
>it's slightly faster processing, to be activated.

  Doesn't this violate the open/closed principle, to make explicit checks
like this?  Or I suppose you could consider this a specific optimization
to ellipses, rather than an explicit check for circles.

 -PD
-- 
--
Patrick Doyle
doylep@ecf.utoronto.ca
