Path: utzoo!utgpu!watmath!clyde!att!whuts!homxb!hound!rkl1
From: rkl1@hound.UUCP (K.LAUX)
Newsgroups: comp.lang.c
Subject: Re: gets(3) nonsense
Message-ID: <2747@hound.UUCP>
Date: 15 Nov 88 17:16:47 GMT
References: <867@cernvax.UUCP> <645@quintus.UUCP> <339@igor.Rational.COM> <1403@unisoft.UUCP>
Organization: AT&T Bell Laboratories, Holmdel
Lines: 7


	Well, I suppose that if gets () is capable of overflowing the buffer,
the way to go would be to read the input one character at a time and check
for buffer overflow oneself.  It would be trivial to write a function to do
this, and you only have to do it once and use it from then on instead of gets ()

--rkl