News for hackers. Stuff that matters.
Re:The History, Controversy, and Evolution of the Goto State... by zzo38computer on Monday November 19, 2018 @02:17AM (#18484658)
That is not specific to do with a goto command itself; even if you wrote "break" instead of "goto fail", still the second one is unconditional. But either way, can easily seen that such program is not sense, so, easily to be noticed.

"There are several good coding practices that could have prevented this fault from occurring, such as code reviews, the proper use of indentation or curly braces, and test coverage analysis." Yes, it is true, whether you use goto or not, whether indentation-sensitive syntax is used or not, etc.

Re:The History, Controversy, and Evolution of the Goto State... by RustHacker on Monday November 19, 2018 @06:13AM (#18485592)
Break is technically a goto, albeit a nicer, more well behaved version thereof.
Re:The History, Controversy, and Evolution of the Goto State... by goto11 on Monday November 19, 2018 @07:51AM (#18486018)
'if' is also technically a goto then.
Re:The History, Controversy, and Evolution of the Goto State... by 13of40 on Monday November 19, 2018 @11:34AM (#18487548)
Earlier this year I spent some time implementing a BASIC (actually VBA) interpreter and to support error handling (e.g. ON ERROR GOTO foobar) I ended up translating all of the flow control statements into conditional GOTOs.