Hmm, interesting, Idea. Do you happen to be anywhere near Toronto, so you can take one of my programming classes, or maybe near a community college so that you can learn what modern programming is really about? Or is high school more your speed? The teachers at high school usually know more about teaching than the instructors at community college, but the guys at community college tend to know more about programming, as they (we) usually are programmers first, teachers second, not the other way around. Did you listen to your teachers when they taught you about programming in something more advanced than Commodore 64 Basic?
I've already implimented a limited form of GoTo similar to how Java does it.
How Java uses Goto?
Java disables goto. It is still a reserved word, but it has no valid context (not that it really had a logically valid context within a structured language anyway). But don't just take my word for it. Look at these sites.
From Sun's Java documentation
In the Java programming language, goto is a reserved word; the Java programming language does not have a goto statement. However there are alternative statements that you can use in the Java programming language in place of the goto statement.
Also look at another Sun Java page
Java has no goto statement. Studies illustrated that goto is (mis)used more often than not simply "because it's there". Eliminating goto led to a simplification of the language--there are no rules about the effects of a goto into the middle of a for statement, for example. Studies on approximately 100,000 lines of C code determined that roughly 90 percent of the goto statements were used purely to obtain the effect of breaking out of nested loops. As mentioned above [Earlier in the web page; refer to original document], multi-level break and continue remove most of the need for goto statements.
Or more clearly from another publisher's site
Note: Although goto is a reserved word, currently the Java language does not support the goto statement. Use Branching Statements instead.
Branching statements in Java are while, do ... until, for, if ... else, switch ... case, break, continue, return which are analogous to the structures and keywords we have in AutoIt. The error processing that Java and C++ have are not implemented in AutoIt, but look at @Error for error status information. It is outlined in each function's documentation.
I hope that puts this issue to rest.
Edit: Fix speeling and errors grammatical. Made a couple of points more clear.
Edited by Nutster, 15 September 2005 - 04:41 PM.