Differences between version 6 and previous revision of GoTo.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 6 | Last edited on Sunday, October 3, 2004 4:43:12 pm | by AristotlePagaltzis | Revert |
| Older page: | version 5 | Last edited on Thursday, June 3, 2004 8:41:56 pm | by AristotlePagaltzis | Revert |
@@ -1,7 +1,7 @@
-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 ''
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.
+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
+See GoToStatementConsideredHarmful.
