Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: What's so bad about scanf anyway??? (really what's bad about gets)
Message-ID: <14493@smoke.brl.mil>
Date: 16 Nov 90 10:55:34 GMT
References: <VXogs2w163w@cybrspc> <1990Nov12.014850.14475@melba.bby.oz.au> <879@jonlab.UUCP>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 9

In article <879@jonlab.UUCP> jon@jonlab.UUCP (Jon H. LaBadie) writes:
>Is this just "conventional wisdom", or does something in the choice
>of BUFSIZ for a particular system ensure any overflow protection?

gets() will input arbitrarily long lines.
The only thing really special about BUFSIZ in this regard is that
many UNIX text editors do not support lines longer than that, so
text files containing longer lines are rarely encountered (but
not impossible).