Re: [Jprogramming] Help, please - crash after suspension in J64

2016-03-22 Thread Henry Rich
I stand ready to help by cutting the failing case down if that is called for. But I don't think that's the right first step. This feels like a memory-corruption problem, given that the failure occurs only if debug has been engaged long before, and that I can run lint on smaller files without

Re: [Jprogramming] Tail recursion (bug hijack)

2016-03-22 Thread Pascal Jasmin
fascinating, I'd add: A verb not dependent on its arguments (but still has rank and called once for each item) (Henry calls this a nilad, but I insist nonad is much more fun) - Original Message - From: Henry Rich To: programm...@jsoftware.com Sent: Tuesday, March 22, 2016 4:34 PM Sub

Re: [Jprogramming] Tail recursion (bug hijack)

2016-03-22 Thread Henry Rich
I think we should look at special code for some of the constructs that lead to great inefficiency currently: n&{."_1@:(u/\) y u/\ y to iterate over items of y is inefficient if internal state needs to be passed along between executions of u. The construct above would signal the interpreter t

Re: [Jprogramming] Tail recursion (bug hijack)

2016-03-22 Thread Henry Rich
I am mostly thinking that flexibility would be good. But there are other possible optimizations: 1. An argument to a verb is known to be sorted 2. An argument to a verb is a hash table 3. An argument is known to be 'read-only', and can skip some recopying 4. A result is known to be discardable

Re: [Jprogramming] Tail recursion (bug hijack)

2016-03-22 Thread Thomas Costigliola
What kind of possibilities where you thinking of? Things not related to $: as well? On 03/21/2016 07:19 PM, Henry Rich wrote: Would it make sense for O. to be a conjunction where v is a bitmask indicating the type of optimization requested? There might be many possibilities. Henry Rich On

Re: [Jprogramming] Help, please - crash after suspension in J64

2016-03-22 Thread bill lam
I still think it is easier for developers if you can provide a simple example to reproduce the bug. I agree with Eric. On Mar 22, 2016 8:06 PM, "Henry Rich" wrote: > Thanks Bill. > > I'm not sure taking it farther will help. The point of error may be back > in debug, rather than the place where

Re: [Jprogramming] Help, please - crash after suspension in J64

2016-03-22 Thread Eric Iverson
The latest Jsoftware J engine source is available and it is ready for easy use under the excellent windows visual studio debugger. The best we can promise is that if someone digs in and comes up with a fix that they will provide to Jsoftware, that we will promptly include it in all official releas

Re: [Jprogramming] Help, please - crash after suspension in J64

2016-03-22 Thread Henry Rich
Thanks Bill. I'm not sure taking it farther will help. The point of error may be back in debug, rather than the place where the program crashed. We really need to look at it under a C debugger to see what the problem is. Henry Rich On 3/21/2016 9:33 PM, bill lam wrote: I can trace it segf

Re: [Jprogramming] Help, please - crash after suspension in J64

2016-03-22 Thread Henry Rich
It required printf to lint without flags. I have fixed that now. Henry Rich On 3/21/2016 9:29 PM, 'Jon Hough' via Programming wrote: Henry, you were right... kind of. I was using old versions of lint and dissect. Now I have upgraded to dissect version 4.6.6 lint version 1.18.9 ... and I get

Re: [Jprogramming] Help, please - crash after suspension in J64

2016-03-22 Thread Henry Rich
Thanks. I'll look into it. I must have used a name that is not defined in a clean J session. Henry Rich On 3/21/2016 9:29 PM, 'Jon Hough' via Programming wrote: Henry, you were right... kind of. I was using old versions of lint and dissect. Now I have upgraded to dissect version 4.6.6 lint