> Still doesn't deny the fact goto has powers you never have with
> if-statements. It can be misused (of course), but if handled well, it
> is definitely a great tool to handle errors for instance (no need to
Yes, it is a very good example of a goto usage, but I think the patch
was about something very different, basically it was an if built with
a goto, that is a very bad usage of a goto.
> "Go To Statement Considered Harmful" is an interesting approach, but
> predates the C-language, too.
There is another paper that people usually don't mention, that is
'Structured Programming with go to Statements" by Donald E. Knuth.
Goto using and structured programming are different things, and goto
usage has a good place in structured programming.
> However, I agree with Christoph that this topic and debate are very old.
> Let's focus on more relevant stuff instead and do some work ;).
Yeah, I totally agree with you. Christoph, are you going to apply the
revised version of the patch?
Regards,
--
Roberto E. Vargas Caballero
Received on Sat Jun 07 2014 - 11:06:48 CEST