Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!umd5!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.lang.fortran Subject: Re: Assigned GOTO Message-ID: <12215@mimsy.UUCP> Date: 29 Jun 88 01:37:57 GMT References: <2742@utastro.UUCP> <20008@beta.UUCP> <224@raunvis.UUCP> <1544@microsoft.UUCP> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 27 In article <1544@microsoft.UUCP> bobal@microsoft.UUCP (Bob Allison) writes: >reading [a previous] article I did manage to come up with a feature >which is fairly difficult to implement in C: assigned gotos. I don't >believe C can take the address of a label ... (Some compilers allow it, but that is just a bug.) I am confident that I could convert any assigned GOTO FORTRAN code into something more reasonable, but I am curious: what do people actually use it for? I once did some fairly extensive FORTRAN programming (the alterative was BASIC, without local variables, etc); the only thing I used ASSIGN statements for was to bypass the FORTRAN system to get addresses into arguments to assembly coded support routines. This is, of course, not legal FORTRAN, just useful. (I was emulating IBM's extension where one can say CALL FOO(param, &label1, &label2) ... SUBROUTINE FOO(param, *, *) ... C I forget the exact syntax, but... jump to label1: RETURN 1 END -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris