Xref: utzoo comp.lang.ada:2811 comp.sw.components:372 comp.object:253 comp.software-eng:2240 comp.lang.modula2:1827 comp.lang.misc:3620
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!think!kulla!barmar
From: barmar@kulla (Barry Margolin)
Newsgroups: comp.lang.ada,comp.sw.components,comp.object,comp.software-eng,comp.lang.modula2,comp.lang.misc
Subject: Re: Inheritance & limited private types
Message-ID: <31018@news.Think.COM>
Date: 22 Oct 89 20:22:05 GMT
References: <48695@ricerca.UUCP> <6845@hubcap.clemson.edu> <126675@sun.Eng.Sun.COM>
Sender: news@Think.COM
Followup-To: comp.lang.ada
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 13

In article <126675@sun.Eng.Sun.COM> grover@sun.UUCP (Vinod Grover) writes:
>For those of us without profilers, I suppose, there is no hope. Or perhaps
>we should worry about efficiency before the product has been developed, or
>perhaps not to worry about efficiency at all. 

Making a program efficient without a profiler is like making a program work
without a debugger.  Sure, you can manually sprinkle your code with print
statements and timing statements, but it's not an efficient way to do it.

Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar