GOSUB and SCREEN and closer reading....

[Fairlight]

Y'all catch dis heeyah?  Tyler been jivin' 'bout like:
> Check out the very first line of my post, Mark:
> "This is a question more out of curiousity than anything else; I've already
> coded around it, though it's an ugly kludge using a flag."

There is that.  Apparently I forgot the first sentence by the time I'd
reached the last.

> As for the screen/end thing in a subroutine, I know it terminates
> processing.  I am basically using it as an interrupt, like throwing an
> exception.

Ooooookay.  Weird way to do it, but ok.

> But that has zero to do with the question.  I wasn't asking for someone to
> solve the coding issue - that's trivial.  I just wanted to know if this is
> by design or a bug.

Well my guess is that it's probably under the category of "known
limitation".  I seem to recall gosubs bridging multiple iterations of a
table coming up before, some years back.  -Any- time you processing in a
table and don't resolve all your GOSUB's, you leave them outstanding, if I
remember the discussion correctly.  I don't think it's limited to SCREEN.

Whether that's a bug or a design choice is open to question, if not debate.
Personally, I'd expect a stack like that to be cleared at any endpoint, but
that's possibly just me.

mark->