🚀 go-pugleaf

In article <danpop.808655822@rscernix> Dan.Pop@mail.cern.ch "Dan Pop" writes:

> >I mentioned
> >    cc .... -Dgets=DONT_USE_GETS

[snip]

> Whether you include <stdio.h> or not is irrelevant.  gets() is in the
> implementation namespace, and any attempt to redefine it invokes undefined
> behaviour, whether <stdio.h> is included or not:

I have difficulty with any defence of gets because it allows a program
to have undefined behavior at run time in consequence of an input.  I
think that is a standards issue and, in a perfect world, would argue
that gets should be removed from the standard library.  Given that, I
appreciate any suggestion which assists me to avoid use of this
abomination in my own code and to excise it from code for which I take
responsibility.

> This should end this thread in comp.std.c.  Things which happen to work
> on some implementations are better discussed elsewhere.
> 
> Dan
> --
> Dan Pop
> CERN, CN Division
> Email: Dan.Pop@mail.cern.ch 
> Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland
> 

As indicated above, I disagree.  The standard is not Holy Writ and
deficiencies in it sometimes result in a need for hacking.

--
walter briscoe