Groklaw - Digging for Truth

	When you want to know more...

Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines

ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

You won't find me on Facebook

Donate

No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.

What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments

Sponsors

Hosting:

On servers donated to ibiblio by AMD.

Webmaster

I have no problem with "goto", where appropriate. | 361 comments | Create New Account

Comments belong to whoever posts them. Please notify us of inappropriate comments.

I have no problem with "goto", where appropriate.

Authored by: jesse on Monday, May 21 2012 @ 08:19 AM EDT

Only when they are misused.

The original objections to "goto" are due to the willy-nilly insertion
of goto in programs by the inexperienced.

Minor story- I used to be the Pascal maintainer at school (many many years ago).
There were two bugs in the N. Wirth compilers - both were caused by a goto. The
one I remember best was in comment scanning. The scanner would loose an
"*" if there were an odd number in a comment row at the end. This was
discovered by a student who was blocking out functions with header/trailers of
"(*****)" comments, causing the end comment mark "*)" to be
lost.

The bug was using a "goto" to avoid a double test...
Turned out that these were the only two goto statements in the entire compiler.

Even the best can fail at using a "goto" properly.

[ Reply to This | Parent | # ]

I have no problem with "goto", where appropriate. - Authored by: Anonymous on Monday, May 21 2012 @ 12:41 PM EDT

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )