Re: [Bug-apl] value error when using 'Cut'

2016-02-08 Thread alexweiner
While I agree that the right-operand binding should be as you have defined it (higher than vector notation), maybe I should take a queue from you and just always put parenthesis around the symbol and both operator inputs, which would free me of having to remember binding strengths, which may vary f

Re: [Bug-apl] Copy of dumped WS copies everything

2016-02-08 Thread Blake McBride
I haven't tested yet, but your description sounds perfectly workable to me.  Thanks! Blake Sent via the Samsung Galaxy Note® 4, an AT&T 4G LTE smartphone Original message From: Juergen Sauermann Date: 2/8/2016 8:32 AM (GMT-06:00) To: Blake McBride , bug-apl@gnu.org

Re: [Bug-apl] Copy of dumped WS copies everything

2016-02-08 Thread Juergen Sauermann
Hi Blake, thanks, sort of fixed in SVN 694. It may not work properly, though, if a file was not )DUMPed or modified manually after )DUMPing it. Reason: DUMP files contain APL code that is being executed. Therefore it is in general not deci

Re: [Bug-apl] value error when using 'Cut'

2016-02-08 Thread Jay Foad
FYI Dyalog are considering introducing Cut into a future version of Dyalog APL and would welcome feedback or collaboration on the design: http://video.dyalog.com/Dyalog15/?v=9KOto3xXS3c http://www.dyalog.com/uploads/conference/dyalog15/presentations/D16_Future_Operator_Proposals.zip http://www.dya

Re: [Bug-apl] value error when using 'Cut'

2016-02-08 Thread Juergen Sauermann
Hi Alex, it is not available in GNU APL. There have been many improvement proposals for APL over the years, but many of them have not made it into the ISO standard (which is GNU APL's implementation blueprint). By literals I mean explicit values like *1 2 3 *or *(1 2) 'abc' *or *42* as oppos