13!:19 '' cuts back the stack - it might be interesting to see what effect
this has when you are in the error state since your stack display is
showing nothing.
On Sat, Feb 2, 2019 at 11:11 AM 'Mike Day' via Programming <
programm...@jsoftware.com> wrote:
> Thanks for both points,
> Mike
>
> Plea
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 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
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
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
It also sometimes happened to me, don't know how to recover.
However IIRC it happened when I loaded scripts again during
suspension. Now I always run dbr 0 to exit suspension and
this stack error happened much less frequent.
Sat, 02 Feb 2019, jprogramming написал(а):
> Occasionally I get this sort
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.
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: m
