Path: utzoo!mnetor!uunet!husc6!mailrus!ames!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uxe.cso.uiuc.edu!mcdonald
From: mcdonald@uxe.cso.uiuc.edu
Newsgroups: comp.lang.c
Subject: Re: gotos (actually: **Apology**)
Message-ID: <225800022@uxe.cso.uiuc.edu>
Date: 18 Apr 88 13:04:00 GMT
References: <2586@geac.UUCP>
Lines: 22
Nf-ID: #R:geac.UUCP:2586:uxe.cso.uiuc.edu:225800022:000:787
Nf-From: uxe.cso.uiuc.edu!mcdonald    Apr 18 07:04:00 1988


Why use goto's? Simple: because it makes sense in the context of the
problem at hand.

FLAME ON ... TEMPERATURE 100,000,000 degress !!!  1e28 tons of helium
ready to turn into Nickel56!!!!!!! (ask sci.astro)


I am FED UP with goto bashers! I'll admit that code filled with gotos
may be messy: if I write a goto, it's because I feel like it! I don't
give a DAMN whether you like goto's or not; I believe in using whatever 
tool is at hand to get the job done. I frankly don't believe for
ONE CLOCK TICK OF A CRAY 2 that gotos make code worse. Spaghetti is
spaghetti, whether it is done with gotos or some other construct, and
so is any other equivalent mess.


But keep up the battle; I'll agree it is worth a good chuckle.

Doug McDonald
Professor of Chemistry
University of Illinois