Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!ames!amdahl!pacbell!sactoh0!jak
From: jak@sactoh0.UUCP (Jay A. Konigsberg)
Newsgroups: comp.unix.wizards
Subject: Re: The *ART* of Computer Programming
Message-ID: <2666@sactoh0.UUCP>
Date: 5 Mar 90 02:05:40 GMT
References: <1990Feb26.234217.23251@aucs.uucp> <732@sppy00.UUCP> <25eb63c7.6a42@polyslo.CalPoly.EDU> <12533@nigel.udel.EDU> <1990Mar2.095746.21311@bath.ac.uk>
Reply-To: jak@sactoh0.UUCP (Jay A. Konigsberg)
Organization: SAC-UNIX, Sacramento, Ca.
Lines: 20

>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.  

There are many times a program seems like its a one-timer, though
the mood of the net is correct, it will probably be reused if it is
at all useful. My solution for Bourne Shell scripts was to write a
program generator that provides much of the formatting, input, file
handeling and trap code needed. Though most of the options are
prompted for, it is now possible to write a "one-time" shell script
that is 80% generated code and very tight.
 
One note here, this program is always in development and I keep as
a programmers program. Therefore, it doesn't always look as good as
the code it produces - oh well.


-- 
-------------------------------------------------------------
Jay @ SAC-UNIX, Sacramento, Ca.   UUCP=...pacbell!sactoh0!jak