Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!megatest!pat
From: pat@megatest.UUCP (Patrick Powers)
Newsgroups: comp.software-eng
Subject: Re: Effect of reuse on speed/reliability/testing
Message-ID: <14910@megatest.UUCP>
Date: 20 Jan 91 07:37:47 GMT
References: <16514.9101161849@olympus.cs.hull.ac.uk> <6076@stpstn.UUCP>
Organization: Megatest Corporation, San Jose, Ca
Lines: 14

> You then
> have to hope that the person who *did* code it made it fast enough for
> your requirements. 

I tried to include execution speed in the manual pages for a library
once but the company at which I worked vetoed this.  It might provide
ammunition for competitors, and besides nobody else provides it, so why
stick out the neck?  I agree with the decision, becauses other
manufacturers could have published false or misleading execution speed
data and we might have lost sales because of it.  However I wish less
vulnerable companies like Sun would publish info of this nature.
Everyone knows it's important.
-- 
--