note hsmyers For those who are interested, here is a <A HREF="http://www.acm.org/classics/oct95/">link</A> to one of the reasons behind the cargo cult notion of no gotos. This of course is “Go To Statement Considered Harmful”, E. Dijkstra's famous letter to the editor of Communications of the ACM, Vol. 9, No. 5 (May 1966), pp. 366-71. Like the basis of many such things, it doesn't quite say what many think—and in any event, should be read by anyone who programs or even pretends to program! Another article that should be read in this context is found <A HREF="http://pplab.snu.ac.kr/courses/PL2001/papers/p261-knuth.pdf">here</A>. Actually the link is to a .pdf file created from scanner input. But still legible for all of that. This paper, “Structured Programming with go to Statements”, is by Donald Knuth, published in Current Trends in Programming Methodology, Vol. 1, Raymond T. Yeh, ed., New York, NY., 1977. In it Knuth details a history of the go to discussion and then follows with his position and rationale. This pair make a good start, but only a start. If you want more before you come to an informed opinion, try Classics in Software Engineering Editied by Edward Nash Yourdon, New York, NY., Yourdon Press, 1979. While sadly out of print, this shows up from time to time at Powell's Technical in Portland. Try <A HREF="http://www.powells.com/technicalbooks">http://www.powells.com/technicalbooks</A> –hsmp.s. Do I use gotos? Of course I do, I'm an assembler hack—can't get there from here without them! 129788 129788