It does not seem onerous that a definition be named for it to be handled by the debugging facilities.
A rule of thumb: if you can not figure out where in a tacit defn is the error, the defn is probably too long and you should split it. ----- Original Message ----- From: "greg heil" <[EMAIL PROTECTED]> To: "Beta forum" <[email protected]> Sent: Wednesday, May 31, 2006 5:24 PM Subject: Re: [Jbeta] J IDE On 5/31/06, Chris Burke <[EMAIL PROTECTED]> wrote: > How to quantify "not getting much mileage"? The debugger is not perfect, but > most things work pretty well, and I use it all the time. What specific things does it lack? There seems to be no way of teasing a tacit apart. No indication of where the failure occurred - i know that is hard to provide. System code likes to run lean and lacks the back out traces. But it would be nice to get the values of [ and ]. For some reason the stack always reports x and y empty ... It would be nice if one could put a marker inside the tacit and get the value when it reaches that point. Ie internal stop/traces ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
