Re: WISHLIST.TXT

new topic     » goto parent     » topic index » view thread      » older message » newer message

On  0, Kat <gertie at PELL.NET> wrote:
> 
> On 23 Aug 2002, at 17:54, christian.cuvier at education.gouv.fr wrote:
> 
> > 
> > ----- Original Message -----
> > From: "Derek Parnell" <ddparnell at bigpond.com>
> > To: "EUforum" <EUforum at topica.com>
> > Sent: Friday, August 23, 2002 4:51 PM
> > Subject: Re: WISHLIST.TXT
> > 
> > 
> > > Not really. By "end loop" I assume you are telling the interpreter to
> > finish
> > > looping through the current loop block. If so, what is the difference
> > > between "end loop" and the current "exit" statement?
> > >
> > 
> > Not really. I'd like to tell the interpreter to finish the current iteration
> > in
> > this loop block and immediately start next iteration. So, current *exit*
> > transfers control after end of block, and *end loop* would transfer control
> > to
> > top loop statement. Thus they differ.
> 
> Yet another arguement FOR goto! It's one word, and it does what it says:
> 
> 
> :restartloop:
> -- initvars
> for loop = 1 to something do
>  --code
>   if whatever1 then goto restartloop end if
>   if whatever2 then goto endloop end if
>   if whatever3 then goto resumeloop end if
> --code
> :resumeloop:
> -- possible code
> end for
> :endloop:
> 
> Kat
> 

Well, after reading this thread, I'll try to seperate from rparse.ex a
gparse.ex (i.e. a goto-only parser of course). If anyone has some hints
abot how to clean up rparse's goto conversion code so the final product
looks neater (by conversion code I mean the code outputed from rparse,
not
rparse's own code, which will always be messy :) I'd be glad to hear
them.

jbrown


--

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu