Re: [Bug-apl] segmentation fault in svn 639

2015-06-20 Thread alexweiner
I think the problem is incorrect parsing. Note that there is no space between between the 'x' and the first '5'. you can also get a segfault if you use ⎕nc and a similar syntax. Its weird because ⎕nc5 and ⎕ex5 result in Domain errors as expected. It looks like the stack trace for both these functio

Re: [Bug-apl] segmentation fault in svn 639

2015-06-20 Thread Juergen Sauermann
Hi, the stack trace (or segfault on some systems) should be fixed in SVN 640. While ISO proposes domain error, APL2 actually returns 0 instead (and so does GNU APL). I'll leave it that way. Thanks, Jürgen

Re: [Bug-apl] segmentation fault in svn 639

2015-06-20 Thread Kacper Gutowski
On Sat, Jun 20, 2015 at 12:32 PM, Louis Chretien wrote: > I agree the error message should not be as dire as a segfault, but the basic > intent seems dubious… There's nothing inherently wrong with this. Argument of ⎕EX should be a character array with rows containing identifiers (possibly padded

Re: [Bug-apl] segmentation fault in svn 639

2015-06-20 Thread Louis Chretien
Why would you want to EXpunge an expression? Isn’t Quad-EX used to delete APL objects? The APL2 manual states that the argument should be the name of an APL object in quotes. I agree the error message should not be as dire as a segfault, but the basic intent seems dubious… > On 2015-06-20, a