Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site wlcrjs.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!wlcrjs!jjd
From: jjd@wlcrjs.UUCP (Joe Durnavich)
Newsgroups: net.lang.c
Subject: Program speed
Message-ID: <666@wlcrjs.UUCP>
Date: Fri, 5-Apr-85 23:57:53 EST
Article-I.D.: wlcrjs.666
Posted: Fri Apr  5 23:57:53 1985
Date-Received: Sun, 7-Apr-85 03:24:17 EST
References: <230@tellab2.UUCP> <135@mit-athena.UUCP> <5399@utzoo.UUCP>
Reply-To: jjd@wlcrjs.UUCP (Joe Durnavich)
Organization: chi-net, Public Access UN*X, Chicago IL
Lines: 17
Summary: 

In article <5399@utzoo.UUCP> henry@utzoo.UUCP (Henry Spencer) writes:

>> ...After all, what does it gain a man
>> to save a millisecond of his computer's time if he loses an hour
>> of his own time thereby?
>
>Sometimes it saves his successor from spending many hours figuring out
>how to get that millisecond out.  Yes, Virginia, some programs do have
>to run fast, and few are the worse for a speed improvement.

Careful Henry!  Take a look at some interpreted BASIC programs.
You know, the ones with 18 statements on one line for "speed improvement"
purposes.  Sure they run fast, but what a bear to read and maintain.
Speed is not always everything.

                                       Joe Durnavich
                                       ihnp4!wlcrjs!jjd