Hi Blake, thanks, fixed in SVN 335.
/// Jürgen On 06/20/2014 05:48 PM, Blake McBride wrote:
It is improved, and the way you deal with comment lines is fine too. However, the following is still important:∇test [1] x←33 [2] →4 [3] x←44 [4] x←55 [5] ∇ T∆test←⍳4 test test[1] 33 test[4] 55 I need a trace line between the two trace lines that says: test[2] →4 IBM APL gives that additional trace line. Thanks. BlakeOn Fri, Jun 20, 2014 at 10:02 AM, Juergen Sauermann <[email protected] <mailto:[email protected]>> wrote:Hi Blake, thanks, fixed in SVN 334. In GNU APL, pure comment lines without statements do not go into the function body and can therefore not be traced. /// Jürgen On 06/20/2014 06:08 AM, Blake McBride wrote:I have to add, this problem with trace renders the trace facility very significantly crippled. For example, I am trying to debug a function I am having trouble with. Since so many lines contain branches or calls to functions that don't return values, I have no idea what is going on. Thanks. Blake On Thu, Jun 19, 2014 at 11:04 PM, Blake McBride <[email protected] <mailto:[email protected]>> wrote: I checked, GNU APL also doesn't print branch lines. IBM APL shows: test[4] →2 in the trace (if it branched to line 2). Thanks. Blake On Thu, Jun 19, 2014 at 10:57 PM, Blake McBride <[email protected] <mailto:[email protected]>> wrote: Trace should show that it executed each line even if that line doesn't produce a value. i.e. GNU APL: ∇test[⎕]∇ ∇ [0] test [1] ⍝ a comment [2] test2 [3] x←4 ∇ ∇test2[⎕]∇ ∇ [0] test2 ∇ T∆test←⍳3 test test[3] 4 IBM APL 2: ∇TEST[⎕]∇ ∇ [0] TEST [1] ⍝ A COMMENT [2] TEST2 [3] X←4 ∇ ∇TEST2[⎕]∇ ∇ [0] TEST2 ∇ T∆TEST←⍳3 TEST TEST[1] TEST[2] TEST[3] 4 Thanks. Blake
