Thanks for both points, Mike Please reply to mike_liz....@tiscali.co.uk. Sent from my iPad
> On 2 Feb 2019, at 16:09, Henry Rich <henryhr...@gmail.com> wrote: > > I think 13!:0 (0), when it takes you out of debug, cuts the stack back. The > code is dense & I will wait till I have a failing case in hand before trying > to penetrate it. > > Re: 2!:55, Yes, that's the point. If the error is flagged when you are > executing a name, perhaps NOT executing a name will work. That is, when you > type exit'' you are failing before you get to the 2!:55. > > Henry Rich > >> On 2/2/2019 11:05 AM, 'Mike Day' via Programming wrote: >> Thanks, Henry. >> >> It’s in the nature of the beast that it’s difficult to reproduce the >> circumstances! Who knows when it’s going to happen? Anyway, as far as I >> recall, debug wasn’t “on” when the stack error occurred. >> >> Meanwhile, should 13!:0 (0) remove the stack error, allowing continuation >> of the session. >> And isn’t 2!:55’’ just the unnamed equivalent of exit’’? >> >> All the best, >> >> Mike >> >> >> Please reply to mike_liz....@tiscali.co.uk. >> Sent from my iPad >> >>> On 2 Feb 2019, at 14:59, Henry Rich <henryhr...@gmail.com> wrote: >>> >>> Try >>> >>> 13!:0 (0) >>> >>> to turn off debug. 13!:0'' leaves it unchanged. 13!:17'' tells you the >>> current debug state. >>> >>> To exit you might try >>> >>> 2!:55'' >>> >>> rather than using the name, since stack errors are tested for when names >>> are executed. >>> >>> If you are in debug, the system hasn't done anything wrong yet. It want to >>> leave the stack for you to look at. It's a bit inelegant not to be able to >>> execute any name at all, I admit. If going out of debug doesn't fix it, >>> give me an example I can reproduce the problem with. >>> >>> >>> Henry Rich >>> >>>> On 2/2/2019 5:12 AM, 'Mike Day' via Programming wrote: >>>> Occasionally I get this sort of thing happening. I've (usually?) used debug >>>> earlier in the session for tracing through a verb or three: >>>> >>>> Today: >>>> >>>> load 'c:/d/j807/user/myscript.ijs' >>>> |stack error: mpart >>>> >>>> ... so I try again, hoping it disappears (!) >>>> >>>> load 'c:/d/j807/user/myscript.ijs' >>>> >>>> |stack error: mpart >>>> >>>> | mpart =:3 :0 >>>> >>>> |[-35] c:\d\j807\user\partition.ijs NB. * >>>> >>>> |stack error >>>> >>>> >>>> JVERSION >>>> >>>> |stack error >>>> >>>> >>>> ... this time I looked up the debug foreigns and tried >>>> >>>> 13!:0 '' >>>> >>>> |stack error >>>> >>>> ... and ... >>>> >>>> 13!:1 '' >>>> >>>> |stack error >>>> >>>> >>>> Is there any cure apart from >>>> "have you tried switching it (J) off and on again?" ? >>>> to which the answer is >>>> "yes - I know that works but it's so crude, and I'd prefer to keep >>>> the session going and not lose the terminal output." >>>> >>>> Not to mention: >>>> >>>> exit'' >>>> |stack error >>>> >>>> >>>> so needing Task Manager (if Windows) or some such to kill the J process. >>>> >>>> Thanks, >>>> >>>> Mike >>>> >>>> *my various partition function, since you ask >>>> >>>> PS: (from a new session!) - not that the version is particularly relevant >>>> - i've had >>>> this happening for years - only thought to ask just now! >>>> >>>> JVERSION >>>> >>>> Engine: j807/j64/windows >>>> >>>> Release-b: commercial/2019-01-22T18:51:16 >>>> >>>> Library: 8.07.22 >>>> >>>> Qt IDE: 1.7.9/5.9.6 >>>> >>>> Platform: Win 64 >>>> >>>> Installer: J807 install >>>> >>>> InstallPath: c:/d/j807 >>>> >>>> Contact: www.jsoftware.com >>>> >>>> >>>> >>>> --- >>>> This email has been checked for viruses by Avast antivirus software. >>>> https://www.avast.com/antivirus >>>> ---------------------------------------------------------------------- >>>> For information about J forums see http://www.jsoftware.com/forums.htm >>> >>> --- >>> This email has been checked for viruses by AVG. >>> https://www.avg.com >>> >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
