In article <61j175F1svdtbU1@[EMAIL PROTECTED]
>,
Paul Russell <prussell@[EMAIL PROTECTED]
> wrote:
> you could
> just invest a little time making the code more robust - it would
> probably be a net win in the long run.
This is the fourth time I have ****ted the software in 30+ years. I am
67 and will probably never have to ****t it again :-). Nevertheless, the
time required to re-write all the code versus the time required to ****t
it every 5-10 years makes the minor fixes worthwhile.
The fact is, I had to ****t 10 C programs (and 27 ksh scripts), of which
9 compiled and ran with no problems. (All the ksh scripts required me
to add '#!/bin/ksh' in the first line because OS X did not default to
ksh, but after that, they ran fine as well). The tenth used the same
module one of the 9 used and had a problem only because I added code for
it a number of years ago in a very quick and unusually dirty way.
Bottom line is most of the code was pretty clean going in and I have
re-done this problem in a proper fa****on to store character strings of
the correct size.
I am sure there are a number of other hidden gotchas buried in this
code, but thankfully, I probably won't have to worry about them.
--
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
|
