Difference between fgets and gets

[user923005]

whilst I don't think Chuck added much with his comment I'd rather
newbie programmers walked around with the idea in their heads "gets is
impossible
to use safely" than the potentially dangerous "gets is nearly
impossible to
use safely".

I'm curious, have you ever written a program that ran in such a
"marshalled"
environment that used gets() safely. And why didn't you use fgets()?

I like Jack's getsafe(). It's not perfect, but it is a lot safer than
gets() and it is not more difficult to use than gets():
http://home.att.net/~jackklein/ctips01.html#safe_gets

 

[CBFalconer]

(e-mail address removed) wrote:
.... snip ...


I like Jack's getsafe(). It's not perfect, but it is a lot safer
than gets() and it is not more difficult to use than gets():
http://home.att.net/~jackklein/ctips01.html#safe_gets

As long as we're recommending replacements, try ggets. Completely
standard C coding, so it will operate anywhere. Safe.

<http://cbfalconer.home.att.net/download/ggets.zip>

 

[Richard Bos]

I was referring to this (hypothetical and iffy case):

Highly iffy; it presumes that you have full control over your execution
environment, which requires the aforementioned constrictive leatherwork.

Richard