A Conversation for The GOTO Statement
xyroth Started conversation Apr 2, 2001
It might be an idea to point out that this statement is usually used to get around the lack of a better structure in the language. It is also essential for error trapping.
SchrEck Inc. Posted Apr 3, 2001
xyroth, thanks for your comments. This would surely be worth including, but I don't know at the moment how to get this done, as it is an edited entry which I couldn't change myself. I'll have to forward the desired changes to the in-house editors who would then update the entry.
Bright Blue Shorts Posted Apr 3, 2001
I think the general rule was that GOTOs were ok as long as they stayed within the same section/procedure of code. As Xy suggests GOTOs are essential in certain languages due to lack of alternative syntax. COBOL is a fairly good example.
SchrEck Inc. Posted Aug 13, 2001
Researcher 196754 Posted Jun 20, 2002
GOTOs are *not* essential for error trapping except in some primitive languages such as VB (I know, I know - it has quite powerful libraries, but the core language is primitive).
Look at Java, C++, PL/SQL and dozens of other high-level languages.
xyroth Posted Jun 21, 2002
I would be interested to find out about a language that didn't need goto, as even versions of prolog and list have needed to add something similar to an unconditional jump.
ps thanks for telling me about the update.
Key: Complain about this post