On 5/29/2011 1:38 AM, Karl Glazebrook wrote:
My main irritation with NiceSlice is it does not work in the debugger.
Anyone know a solution to that?
I don't know if this is a solution or a workaround
but you could use the perldlpp.pl script in the
PDL/utils directory to pre-process the NiceSlice
constructs for your code. At that point you have
just plain perl code which should run in the debugger
just fine.
In fact, if you convert your *.pm files and save
the pre-processed version as the corresponding
*.pmc in the same location then the perl interpreter
should pick them up instead of the .pm files.
On 29/05/2011, at 1:59 AM, David Mertens wrote:
The basic problem is that a source filter simply reads in text and
applies overly simple text processing methods to do magic. This means
that most source filters are fragile, and when they break the errors
can be very weird. Source filters also do not (did not?) work with
modperl.
A key point is that "most source filters are fragile"
*because* they apply "overly simple text processing
methods to do magic". While it is difficult/impossible
to completely handle all possible perl-mutations, we
can definitely do better with PDL::NiceSlice by
refactoring PDL::NiceSlice to use Module::Compile:
* Allows NiceSlice off-line processing via 'perl -c'
* Use of .pmc files should allow debugging to work
* NiceSlice constructs in POD and strings could be skipped
* Automated lvalue sub workaround insertion (yuck!)
* Runtime resolution of sub refs vs pdls in $a->()
See the following open tracker items for reference:
http://sourceforge.net/tracker/?func=detail&aid=3018731&group_id=612&atid=100612
http://sourceforge.net/tracker/?func=detail&aid=3074830&group_id=612&atid=350612
Cheers,
Chris
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
