The main tools (Stop manager, Watch manager, Stack view) are enabled as
soon as you press ctrl+K, even if you haven't run anything.
Henry Rich
On 1/2/2017 7:50 PM, bill lam wrote:
even all boxes had been grayed out. If it runs into any error, J will enter
into suspension mode showing the offen
even all boxes had been grayed out. If it runs into any error, J will enter
into suspension mode showing the offending lines and stack. I think gui
debug is normally used in this way.
On 3 Jan, 2017 8:33 am, "Moon S" wrote:
> Dunno.. Ctrl+K just shows the debug box with all options grayed. The
Dunno.. Ctrl+K just shows the debug box with all options grayed. The secret
knowledge was dbstop. No GUI to set a break-point at a line or all lines,
no right button action, no way to start line-by-line execution from the
menu or toolbars. Just dbstop.
On Tue, Jan 3, 2017 at 2:11 AM, bill lam wro
debug utility is now contained inside stdlib, no longer needed to load
'debug'
press ctrl-k should be enough to run the gui debug.
On 3 Jan, 2017 7:08 am, "chris burke" wrote:
> See the lab: Help|Studio|Labs|Debug
>
> In brief, load debug with:
>
>load 'debug'
>
> and press Ctrl-K to show
── (2 of 28) Activating Debug ───
The Debug help file is in User Manual|Debug. Take a few
minutes to browse the help. You may also refer to it as you
go through the lab.
)
User Manual|Debug? User Manual where?
── (8 of 28) Stepping through a definition (ctd)
See the lab: Help|Studio|Labs|Debug
In brief, load debug with:
load 'debug'
and press Ctrl-K to show the debugger.
On Mon, Jan 2, 2017 at 2:11 PM, Moon S wrote:
> 1) JQt (8.05, j64, windows, all latest) can't debug a program. I mean, run
> it line by line, entering or stepping over functi
I can reproduce this.
Henry Rich
On 1/2/2017 4:37 PM, Mark Allen wrote:
I'm running j64-805 on a Mid 2012 MacBook Air with 8GB RAM.
I have a script that causes jqt to crash. The script implements the F(m,n)
function as described in here: https://projecteuler.net/problem=115 and is
as follows:
1) JQt (8.05, j64, windows, all latest) can't debug a program. I mean, run
it line by line, entering or stepping over functions. At least I couldn't
find how to do it. Moreover, it can't run a program: file > open > latest
... someprogram.ijs --> new edit window with green background pops up, then
I'm running j64-805 on a Mid 2012 MacBook Air with 8GB RAM.
I have a script that causes jqt to crash. The script implements the F(m,n)
function as described in here: https://projecteuler.net/problem=115 and is
as follows:
params =: ( <:@:i.@:(] - <:@:[))
coeffs =: (|.@:>:@:i.@(] - <:@:[))
f =
if expensive, you should go with one of the other options provided. Either
^:["0 or @.["0. ^: is usually faster of 2.
If the operation is cheap though (such as >:), (* >:) is actually much faster
as no test is made.
- Original Message -
From: David Koppenhoefer
To: programm...@jso
J isn't a lazy language, so the programmer is required to be lazy instead.
In other words, it looks like you are interested in some of the following:
M. http://www.jsoftware.com/help/dictionary/dmcapdot.htm
^: http://www.jsoftware.com/help/dictionary/d202n.htm
if. http://www.jsoftware.com/help/
Ask, and you shall be covered in gifts :-)
But I have a follow-up question. The function that actually should be
applied is rather expensive (it is the distance function of the
labyrinth of AoC 24), so it should only be executed on the selected
values. This seems not to be the case in
0 0 1 0 0
12 matches
Mail list logo
