gets(3) nonsense

K.LAUX rkl1 at hound.UUCP
Wed Nov 16 03:16:47 AEST 1988


	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



More information about the Comp.lang.c mailing list