Xref: utzoo comp.bugs.4bsd:1675 comp.std.c:4193 comp.lang.c:35521
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!agate!shelby!unix!garth!smryan
From: smryan@garth.UUCP (Steven Ryan)
Newsgroups: comp.bugs.4bsd,comp.std.c,comp.lang.c
Subject: Re: Safe coding practices (was Re: Bug in users command)
Message-ID: <60@garth.UUCP>
Date: 26 Jan 91 02:13:25 GMT
References: <1991Jan25.021929.10512@tkou02.enet.dec.com> <22878@well.sf.ca.us>
Reply-To: smryan@garth.UUCP (Steven Ryan)
Organization: INTERGRAPH (APD) -- Palo Alto, CA
Lines: 15

>No, of course that's not what I mean.  It checks for overflow, tells
>you that it needs to be recompiled on overflow, and aborts on
>overflow.  Why is that so hard to understand?  Complete source is

Recompile what? Is the source always available? Is the build process
properly documented and all build files available? Is the routine
coded so that Joe Average can fix, recompile, and continue in five
minutes? Do you what Joe Average is going to think of you afterwards?
Do you think he'll be eager to run anything else with your name on
it?

Why is it difficult for so-called programmers to avoid arbitrary limits?
-- 
...!uunet!ingr!apd!smryan                                       Steven Ryan
...!{apple|pyramid}!garth!smryan              2400 Geng Road, Palo Alto, CA