Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!mips!bridge2!jarthur!elroy.jpl.nasa.gov!george!alan
From: alan@george.Jpl.Nasa.Gov (Alan S. Mazer)
Newsgroups: comp.unix.wizards
Subject: Re: The *ART* of Computer Programming
Summary: one-time program?
Message-ID: <1990Mar1.233732.22488@elroy.jpl.nasa.gov>
Date: 1 Mar 90 23:37:32 GMT
References: <1990Feb26.234217.23251@aucs.uucp> <732@sppy00.UUCP> <12533@nigel.udel.EDU>
Sender: news@elroy.jpl.nasa.gov (Usenet)
Organization: Image Analysis Systems Grp, JPL
Lines: 15

In article <12533@nigel.udel.EDU>, new@udel.edu (Darren New) writes:
> In article <25eb63c7.6a42@polyslo.CalPoly.EDU> jdudeck@polyslo.CalPoly.EDU (John R. Dudeck) writes:
> >If a program is worth >writing it is worth writing well.  
> Have you never heard of a one-time program? Or were you not referring to
> this kind of program?     -- Darren

What is a one-time program?  Is that a program to solve a problem that
will never come up again?  I don't think there's any such thing.  Either
you rewrite it next time you need it, or you have to figure out your old
code, or you write it well the first time.  I agree with the original
statement.

-- Alan				# "But seriously, what could go wrong?"
   ..!cit-vax!elroy!alan
   alan@elroy.jpl.nasa.gov