From: no.email@nospam.invalid   
      
   albert@spenarnc.xs4all.nl writes:   
   > I maintain that if you are not in a recursive call for   
   > a function with locals, and you try to catch the same function   
   > call, everything is fine.   
      
   The thing about exceptions is that they occur unexpectedly.  Example:   
   your recursive function prints something, and that works the first few   
   times, but then the printer runs out of paper and there is an i/o   
   exception.  It's not the recursive function's job to handle this.  The   
   exception throws to some outer level handler that asks the user to fix   
   the problem.   
      
   Adding (LOCAL) to a Forth interpreter should normally not be too   
   difficulot, if you control the interpreter implementation.  It's the   
   right way to do stuff like this.  Why mess around with all that awful   
   stack juggling for a half-working and woefully slow solution?   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)