Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!gatech!udel!mmdf
From: tweten@gilmore.nas.nasa.gov (Dave Tweten)
Newsgroups: comp.os.minix
Subject: Re: Re: Fixing 7K pipes again
Message-ID: <24962@louie.udel.EDU>
Date: 28 Sep 89 19:11:00 GMT
Sender: mmdf@udel.EDU
Lines: 18

From: Andy Tanenbaum 

	This is definitely a nono.  No gotos please!

I hope you are merely overstating you case, Dr. Tanenbaum.  I had
thought the "No gotos" religion had died, mercifully for the rest of
us.

I continue to find that something on the order of one "goto" per 5000
lines of C code or so is required to maximize simplicity, clarity and
therefore maintainability.  Applications include breaking out of two
levels of loop at once, breaking out of a loop, but not executing the
loop exhaustion code, switch cases which should decide to break out of
the surrounding loop, etc., etc.  I didn't see enough context to tell
if the specific "goto" which triggered your message was a good one, but
surely an absolute "No gotos" is not a defensable position.

Please say you were kidding.