Nested "Select Case"s

[picster]

Are there any problems (besides being visually confusing) that one would encounter with nested "select case" routines, and if not, is there a limit to depth - i.e.- are 3 ok?

Thanks

[HenrikOlsson]

No problems that I know of, have done it many times though not that many levels (2-3).
I don't know if there's a limit, can't think of why there would be.

/Henrik.

[Demon]

The only limit I can think of is the "stack". But that's most likely the same stack we use for GOSUBs and nobody has complained about a limitation on that yet.

"Total deduction on my part without a shred of supporting evidence"

Robert

[Jerson]

A select case statement expands to a sequence of 'If This Then That' constructs when run through the compiler. Since there is no limitation using the If then, I do not anticipate a limit on the nesting of select case statements. Gosubs are in a different category wherein the compiler can decide to use the stack - or in some cases - to use gotos to acheive the same functionality and is totally compiler dependent.

[picster]

Good to know, thanks!!

[Demon]

...Gosubs are in a different category wherein the compiler can decide to use the stack - or in some cases - to use gotos to acheive the same functionality and is totally compiler dependent.

Ok, you got me on that one. How can GOTOs be used to achieve GOSUB logic?

The going part is not a problem, but how does it come back without using a stack or some such memory to remember where it came from?

Or does it replace the RETURN with a GOTO pointing to the statement following the GOSUB?

Robert

[pedja089]

I dig many .LST files, and didn't see that compiler replaces GOSUB with GOTO.
ON DEBUG uses GOTO after each PBP line, but before GOTO saves address to DEBUG_ADDRESS and, DEBUG_ADDRESSU variables. So you can use them to load program counter to get back from where PC jumped.