Dan - I ran into this situation recently. I had cut and pasted some session code into a function. I was being lazy and reloading a script within the function instead of loading it once and saving what needed to be re-initialized. An error inside this somehow filled up the stack and I found myself in the situation you describe. Moving the "load" code outside the function definition appeared to fix the problem.
You're right that it would be nicer to be not so dead in the water in such a situation. Regards, Devon On 7/12/08, Dan Baronet <[EMAIL PROTECTED]> wrote: > > Hi, > > I decided to 'upgrade' an app I had running under V5.0x to 6.01 and after > going thru the changes (not too many) I have it sort of going. > Except that I hit a problem deep down somewhere. > > Hard to tell what is happening without a stack so I decided to use the > debugger. > Thing is when a problem occurs the debugger fills up the stack and I end up > in a situation where I cannot enter anything, not even 13!:0]0 to clear the > stack. > Worse, I cannot even exit from J to restart it as all the menu/buttons > display stack error. > The problem is likely my fault but shouldn't there be a way to exit J? > > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > -- Devon McCormick, CFA ^me^ at acm. org is my preferred e-mail ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
