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.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Xref: utzoo comp.lang.ada:2808 comp.sw.components:371 comp.object:251 comp.software-eng:2239 comp.lang.modula2:1826 comp.lang.misc:3619
Path: utzoo!attcan!uunet!ginosko!uakari.primate.wisc.edu!xanth!ames!sun-barr!newstop!sun!brahmand!grover
From: grover%brahmand@Sun.COM (Vinod Grover)
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: <126675@sun.Eng.Sun.COM>
Date: 22 Oct 89 07:00:04 GMT
References: <48695@ricerca.UUCP> <6845@hubcap.clemson.edu>
Sender: news@sun.Eng.Sun.COM
Reply-To: grover@sun.UUCP (Vinod Grover)
Organization: Sun Microsystems, Mountain View
List-Id: <comp.lang.ada>

In article <6845@hubcap.clemson.edu> billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu writes:
>   It has long been recognized that the time to worry about product
>   efficiency is AFTER the product has been developed and put through
>   a profiler to determine where the bottlenecks are in the system,
>   since in this way the high cost of maximizing efficiency can be
>   directed to the points at which it will do the most good.

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.