Re: [Jprogramming] how to debug

2020-03-30 Thread Rudolf Sykora
Dear Devon, Devon McCormick writes: > |NaN error: gettplog > | pos=.min+step*i.>:>.(max-min)%step > |gettplog[:11] > ... > > So, I am properly stopped at this point but I can't figure why my initial > stops don't have an effect. At least the above will provide a work-around. although t

Re: [Jprogramming] how to debug

2020-03-30 Thread Rudolf Sykora
Dear Bill, bill lam writes: > You can first isolate problem be related to pop up box by setting > wdinfo_z_=: echo > so there won't be any pop-up info box. > > If crash gone away then it is a jqt issue. with wdinfo_z_ =: echo the crash is gone. I get 'ylog 1' plot 1 2 0 3 ++

Re: [Jprogramming] how to debug

2020-03-29 Thread Devon McCormick
Since I use the debugging every now and then, I thought it would be easy to answer Ruda's question but it was not. My first thought is that the name of the verb in question is not "gettplog" but "gettplot_jzplot_". However there appears to be both "gettplog_jzplot_" and "gettplog_jwplot" which ap

Re: [Jprogramming] how to debug

2020-03-29 Thread bill lam
You can first isolate problem be related to pop up box by setting wdinfo_z_=: echo so there won't be any pop-up info box. If crash gone away then it is a jqt issue. On Mon, Mar 30, 2020, 12:43 AM Rudolf Sykora wrote: > Dear list, > > > if I do > >load 'plot' >'ylog 1' plot 1 2 0 3 > > t

Re: [Jprogramming] how to debug

2020-03-29 Thread Rudolf Sykora
Brian Schott writes: > I think you mean to use > dbss'gettplog * : *' I believe that's essentially equivalent to dbstop 'gettplog' Anyhow, using dbss does not help. Thanks Ruda -- For information about J forums see http://www.

Re: [Jprogramming] how to debug

2020-03-29 Thread Brian Schott
Ruda, I think you mean to use dbss'gettplog * : *' -- (B=) -- For information about J forums see http://www.jsoftware.com/forums.htm

[Jprogramming] how to debug

2020-03-29 Thread Rudolf Sykora
Dear list, if I do load 'plot' 'ylog 1' plot 1 2 0 3 then I get an error message about NaN in 'gettplog'. Something like that is almost expected to happen (but not necessarily, __ coming from log 0 still isn't NaN, or is it?). I wanted to edit gettplog to see what could be done, but first