Actually the stack size is limited. It's the heap that is not. For C and
C++ applications you can set the desired stack size during linking. There
is a flag for it but since I'm on mobile right now it's a bit of a hassle
to check right now.
Regards,
Elias
On 2 Jan 2016 11:01 p.m., "Juergen Sauerma
Hi Blake,
as of now I suspect the problem is not a too small ⎕WA, but a too
large automatic variable on the stack. General problem in *nix-like
OSes
is that they (in practice) never run out of space but begin
swapping instead.
And we alre
Hi Juergen,
Just a thought, perhaps you can change a parameter in GNU APL (for local
testing purposes only) to force a small ⎕wa so that you can simulate the
problem and do so more quickly.
Thanks.
Blake
On Sat, Jan 2, 2016 at 7:55 AM, Juergen Sauermann <
juergen.sauerm...@t-online.de> wrote:
Hi,
I am currently trying to reproduce the fault, but was not yet able
to.
Like in Blake's case, 1500x1500 worked on my machine.
I am currently trying 4000x4000 but that hasn't finished yet
(takes ages).
The _expression_ that I am using i
Just for reference, I tried your example with the head of the source code
repository, and I got:
$ apl
a←1500 1500⍴?(1500×1500)⍴10
⎕wa
732487680
b←⌹a
)off
However, since your ⎕wa was substantially less than mine, it may be that
you ran out of RAM and I didn't.
Also, what
