It appears that if you set $PDL::NiceSlice::debug_filter to true it
should print all the lines to stdout.
--Chris
On 2/26/2015 16:07, Derek Lamb wrote:
On Feb 26, 2015, at 5:12 AM, Chris Marshall <devel.chm...@gmail.com
<mailto:devel.chm...@gmail.com>> wrote:
perldlpp.pl doesn't do the Filter::Simple filtering, just classic...
oh, ok. I guess I didn't look at it that closely. Now that I am, I
don't see how that happens, since that script just calls
PDL::NiceSlice::perldlpp, which is in NiceSlice.pm, which has the
default engine set to Filter::Simple. But maybe I'm missing
something. Setting the PDL_NICESLICE_ENGINE environment variable to
Filter::Simple and Filter::Util::Call and running perldlpp.pl on
PGPLOT/Window.pm produces identical .pmc files, so I probably am
misunderstanding.
(So how does one view the Filter::Simple parsing results? I'd like to
see what it does to Window.pm that causes those syntax errors.)
But if that's true, then the rest of my message probably doesn't apply
to the new engine, and those remaining 9 seconds are for the rest of
the PDL modules (and also PDL::Stats). Yes, "use PDL::NiceSlice" was
commented out in my module after running the .pm through the filter in
utils/perldlpp.pl.
best,
Derek
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pdl-devel
