Nested Gosubs

[Fairlight]

When asked his whereabouts on Mon, Nov 01, 2004 at 12:29:41PM -0500,
Brian K. White took the fifth, drank it, and then slurred:
> >  I'm finding that a bit hard to believe,
> > if all processing -ends- when you hit END or an equivalent (SCREEN).
> 
> Since when does an end command end all processing?

Well, it was incorrectly stated on my part.  I said what I said, rather than
what I meant.

It's meant to end a...subroutine for lack of a better word, or at least the
immediate processing until the next event that triggers more processing
occurs.  It's more like a breakpoint than anything else.

Call it lack of imagination on my part, but I'm finding myself unable to
imagine a scenario where I'd want to intentionally call a subroutine at @w*
processing, have it gosub somewhere and then -end-, and then return at a
later time, based on a wholly different event.  That actually seems like
pretty shaky flow to me, unless you shut all airtight doors between
compartments inbetween the two parts that should happen.

I'm sure you're right and it's perfectly reasonable, if a bit esoteric.
I'm not seeing it mentally, but I shan't debate the point.  You do far more
native UI-based coding than I do anymore.  Most of my work is integration.
I'll just take in on faith that you're correct and that it's useful.  :)

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html