I've found yet another way of crashing J, this time under windows. Something really crazy is going on. For example, I get stack errors from smoutput in a variation of the code where I'm trying to isolate the line that triggers the problem.
Another face of this issue was that last night I was experiencing really long (multiple second) delays when trying to single step through the code. (As an aside: the debugger's breakpoints are broken when dealing with two different verb definitions associated with the same name in different locales. I imagine it would have similar issues with local definitions. Debuggers always have limits, but I think ours might be due for a rebuild, soon...) The good thing about bugs is that they make you look for another way of accomplishing things. The bad thing about them is way too obvious. Thanks, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
