[futurebasic] Re: [FB] GOTO

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : October 1999 : Group Archive : Group : All Groups

From: Bryan Bremner <bremner@...>
Date: Tue, 19 Oct 1999 15:18:37 -0700
LongIF (YourAge < 45 )
	THEN	GOTO NextMessage (Unless you are masochistic)
	ELSE	Listen to maundering_in_beard of OldFart

Talk about your GOTO Sphagetti, have you heard the one about the
ASSIGNED GOTO Sphagetti!

This appeared early in FORTRAN and then moved over to PL/I.

	We are talking about IBM 709, 7090, and 360/60 etc.

ASSIGN 3 to JUMP
GOTO JUMP

If you really want to go wild you could use dimensioned variables.  ie.
GOTO JUMP(ijump)

I puzzled and puzzled over some working code for more than a week until my
puzzler completely broke.  I just walled it off, called it a subroutine and
used it even though I had no idea how it worked.

I did make use of this concept in a PL/I discrete event simulation program
I wrote.  (I will leave description to the terminally curious off list.)  I
think the main thing is to make your code understandable after 6 months.
Sometimes its a GOTO, sometimes its a IF..THEN, sometimes its a CASE, and
sometimes its redesign the whole program.

NextMessage:


Bryan Bremner
bremner@...