Re: During )dump / )copy, )dump / )load cycle the variable content gets lost and oone more stack trace.

Hi Jürgen, thank you. One item less to worry: Best Regards, Hans-Peter Am 28.02.25 um 17:58 schrieb Dr. Jürgen Sauermann: Hi again, forgot the second part. Yes, I believe using )SAVE and )LOAD is safe. Best Rgeards, Jürgen On 2/27/25 13:01, Dr. Jürgen Sauermann wrote: Hi Hans-Peter, the

Re: Missing gap line in output of multi dimentional array

Hi Hans-Peter, I am not sure if your observation below is an error. The relevant rule in the IBM APL2 language reference manual is this (Figure 22 on page 138): /* For Z←R, where R is a nested array:: ...  Z has LN intermediate blank lines between vertically adjacent items C and D, where: LN←0

Re: During )dump / )copy, )dump / )load cycle the variable content gets lost and oone more stack trace.

Hi again, forgot the second part. Yes, I believe using )SAVE and )LOAD is safe. Best Rgeards, Jürgen On 2/27/25 13:01, Dr. Jürgen Sauermann wrote: Hi Hans-Peter, there are ways to improve the )LOAD time. I did a complete rework of 10 ⎕CR, so I wanted to keep things simple in the beginning. T

Re: (lack of) Monadic ≠ in GNU APL ('Nubsieve' / 'Unique Mask')

Hi Russ, I will look into this. One observation so far is that your *Q←{ ((⍵⍳⍵)=⍳⍴⍵)/⍵ }* seems to return the unique elements rather than a boolean vector: *   Q←{ ((⍵⍳⍵)=⍳⍴⍵)/⍵ }   ⎕CR 'Q' λ←λ1 ⍵ λ← ((⍵⍳⍵)=⍳⍴⍵)/⍵   Q 'Hello, World' Helo, Wrd   ∪'Hello, World' Helo, Wrd* Look