Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker.mit.edu!shelby!unix!garth!smryan
From: smryan@garth.UUCP (Steven Ryan)
Newsgroups: comp.lang.c
Subject: Re: Safe coding practices (was Re: Bug in users command)
Message-ID: <76@garth.UUCP>
Date: 1 Feb 91 19:26:52 GMT
References: <87681@tut.cis.ohio-state.edu> <22921@well.sf.ca.us> <11653@helios.TAMU.EDU>
Reply-To: smryan@garth.UUCP (Steven Ryan)
Organization: INTERGRAPH (APD) -- Palo Alto, CA
Lines: 15

>>In general, sure, handling arbitrary input is great.  In specific cases
>>where you can make a confident estimate of the maximum input size, I have
>>no problem at all with using checked fixed size arrays of ten times
>>that size.  The benefit is N fewer lines to get wrong, and the cost, if
>>your estimate is good, is non-existant.

Should all this be moved to rec.humor.c? The first thing the fanatics shout out
each time a Fortro-C War breaks out is that the poor Fortran programmers are
forced to use fixed size arrays, whereas C with its linked lists and
dynamically allocatable arrays can handle anything machine memory size permits.

I guess you can program in Fortran in any language.
-- 
...!uunet!ingr!apd!smryan                                       Steven Ryan
...!{apple|pyramid}!garth!smryan              2400 Geng Road, Palo Alto, CA