Chris, this blows up the memory on my Macbook Air and fills up all the
swap space (clearly there isn't much) and i had to restart the system to
recover it.
The pure perl version is more efficient due to possible perl optimizations.
So the culprit is the $possible = where $possible, $possible %
Yes, maybe some use of -sever to turn off data flow
might allow things to be freed. It is definitely
possible to tend the memory directly in the implementation
to work around the alloc/free issue.
--Chris
On 2/15/2015 08:32, Vikas N Kumar wrote:
Chris, this blows up the memory on my Macbook
Perldl list members-
The current host for the perldl mailing list is
going away at the end of this month. A new list,
pdl-general has been set up at sf.net.
Please join the list as soon as possible by
going to the web interface page at:
I made my own attempt at a solution (attached).
It runs in 6s in a Dell Inspiron N5110 and in 53s in an ASUS
Transformer tablet. So I guess it is fast. It seems correct but I have
some doubts (below)
-- Code:
#!/usr/bin/env perl
use strict;
use warnings;
use feature
