You advocate GOTO because of the single use case: nested resource cleanup. You only focus on this, lone, "good" example.. none of the bad points, you are short sighted. Your short sight prohibits moving on to better control structures. Your type is the same as those that claim stem cell research is immoral on religious grounds, ignoring the fact it could save millions of lives. I hate you.
By ``moving on'' you mean ``using an arbitrarily smaller toolset that doesn't get the job done''. yawn, ihbt
Name:
Anonymous2010-12-10 15:47
Hi, this thread is all about gotos, REAL GOTOS. This thread is awesome. My name is Robert and I can't stop thinking about gotos. These statements are cool; and by cool, I mean totally sweet.
Facts:
1. Gotos are statements.
2. Gotos change execution flow ALL the time.
3. The purpose of the goto is to flip out and jump to a label.
Gotos can jump anywhere they want! Gotos cut off loops ALL the time and don't even think twice about it. These statements are so crazy and awesome that they flip out ALL the time. I heard that there was this goto who was sitting at a nested loop. And when some function dropped an error and the goto jumped out all the loops. My friend Mark said that he saw a goto totally skip some noob code just because the kid opened a window.