I have been working on the debugger & will look into these.
0. I'll check.
1. When you debug a verb with a "header", like
dverb =: 3 : 0"1
...
)
the debugger treats it as a tacit verb and doesn't let you look inside.
It displays like a tacit verb (which in fact it is!), all on one line,
with the LFs replaced by (1{a.). Is this what you are seeing?
To debug it you have to split it into
dverb =: dverbbody"1
dverbbody =: 3 : 0
...
)
In the next release the debugger will do this automatically for you. If
you select dverb for a stop, it will create the body and replace dverb
with a verb that points to the body. Stops will be placed into the body.
Henry Rich
On 5/25/2015 5:31 AM, Jan-Pieter Jacobs wrote:
Writing a cover verb for dsygv in the Lapack addon, I noticed 2 bugs with
the debugger:
0. When you enter a non-existing verb in the "name" field and press enter,
the debugger crashes J. This does not happen for the locale field.
1. The debugger seems to have issues with some types of line endings,
making newlines show up as what the console shows for (1{a.) (gmail seems
to refuse this character here). This seriously hampers debugging, as the
debugger shows all code in one single line when an error occurs or when
setting a "stop Line" in the stop manager.
An example of this can be seen taking a look at
~/addons/math/lapack/geev.ijs.
I presume it's an Unix/Windows line ending issue (I'm on Windows 8.1, 64
bit, most recent J, all addons up to date).
Best regards,
Jan-Pieter
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
