Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.lang.c Subject: Re: goto's Message-ID: <7696@mimsy.UUCP> Date: Sat, 25-Jul-87 18:38:59 EDT Article-I.D.: mimsy.7696 Posted: Sat Jul 25 18:38:59 1987 Date-Received: Sun, 26-Jul-87 02:49:52 EDT References: <3289@bigburd.PRC.Unisys.COM> <7571@beta.UUCP> <765@haddock.ISC.COM> <7687@mimsy.UUCP> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 18 In article <7687@mimsy.UUCP> I mentioned >(The following may be flawed; ... It sure was. >Nonetheless the general idea ought to be right.) ... which I still think is true. The general idea, in case it was obscured by the (bogus) details, is to add enough booleans and, if necessary, a loop around the entire program, so that each goto can be replaced by a sequential flow to the place to which the goto went, where the gone-to code then executes. Doing this is nontrivial, but, I think, always possible. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690) Domain: chris@mimsy.umd.edu Path: seismo!mimsy!chris