search for: f_static_depth

...return value; the next one is the nesting depth to which you want to go (I'm assuming that you can only go to a less nested function); the last one is a number indicating which label in the final function you want to branch to. A non-local goto (to function F, label L) becomes: ret { undef, F_static_depth, L_number } After every call to this function you then check the second return value to see if it is a valid static depth (if not, no non-local goto happened and execution continues normally) and if it is then either: (a) the static depth is that for this function; you then execute a switch stateme...

...the > nesting depth to which you want to go (I'm assuming that you can only go > to a less nested function); the last one is a number indicating which > label in the final function you want to branch to. > > A non-local goto (to function F, label L) becomes: > ret { undef, F_static_depth, L_number } > After every call to this function you then check the second return value > to see if it is a valid static depth (if not, no non-local goto happened > and execution continues normally) and if it is then either: (a) the > static depth is that for this function; you then exec...

The languages I'm faced with compiling in the near future have nonlocal go to statements and nested procedures. A procedure gets implemented as a structure containing its entry point and an environment pointer. It is easy enough to call its entry point and pass the environment pointer as an extra argument (rather like the pointer to this or self in object-oriented code). It's no