Differences between version 8 and revision by previous author of GoTo.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 8 | Last edited on Saturday, May 14, 2005 1:42:28 am | by AristotlePagaltzis | Revert |
| Older page: | version 3 | Last edited on Friday, October 24, 2003 10:38:55 am | by PerryLorier | Revert |
@@ -1,7 +1,14 @@
-A statement in many ProgrammingLanguages
which causes an unconditional branch to an arbitary point in the current function or method. In a host of early [BASIC] dialects, it was the only control structure available besides ''
if''
statements.
+A statement in many ProgrammingLanguage~s
which causes an unconditional branch to an arbitary point in the current function or method. In a host of early [BASIC] dialects, it was the only control structure available besides <tt>
if</tt>
statements.
-Despite being maligned in general use, GoTo is still the best way to describe [
FiniteStateMachine]
s such as parsers in these languages.
+Despite being maligned in general use, GoTo is still the best way to describe FiniteStateMachine~
s such as parsers in these languages.
-It's also used in C programming a lot to provide something resembling "exceptions", particularly "finally" clauses
. You often see "goto out" and then out is a label just before the final return
.
+ The apprentice uses it without thinking
.
+ <br> The journeyman avoids it without thinking.
+ <br> The master uses it thoughtfully
.
-See GoToStatementConsideredHarmful
+It’s also used in [C] programming a lot to provide something resembling “exceptions”, particularly “finally” clauses: a <tt>goto out</tt> where <tt>out</tt> is a label just before the final <tt>return</tt>.
+
+
See GoToStatementConsideredHarmful.
+
+----
+Part of CategoryProgramming
