On 8/17/2011 3:51 AM, Sisyphus wrote:
----- Original Message ----- From: "Sisyphus"
Anyway, I see Chris has just now pushed another release to CPAN ...
I'll wait and see how that fares before digging any further.
Well ... I never could leave a pimple alone.
I think Core.xs.PL might be setting up an incorrect Core.xs. And it may
well be that it has been doing that for quite some time - but without
any undesirable consequences until recent changes to ExtUtils::ParseXS.
According to git, the code in question has been there
since 1998.
The attached patch to Basic/Core/Core.xs.PL seems fine with both 2.2210
and 3.03, without any need to make changes to Basic/Core/typemap. (Still
doesn't work with 3.00_01, but nothing does - I think that version is
broken to such an extent that there's not much point in concerning
ourselves with the problems it presents.)
I think that in the "MODULE = PDL::Core PACKAGE = PDL" section of
Core.xs, whenever the PDL_Long * declaration exists outside of the
CODE/PPCODE section, that now tells this latest xsubpp that this
function is bound to perl and there needs to be a 'PDL_Long *' typemap
entry.
In short, I'm thinking about leaving the typemap as it was, and using
the attached Core.xs.PL patch.
But I'm no expert on XS, so I'm raising the matter here.
I've also just started a thread at perlmonks to see if anyone there has
some views on this recent change to ExtUtils::ParseXS - and on what is
the correct approach to fixing the matter.
For anyone interested, that thread can be found at:
http://www.perlmonks.org/index.pl?node_id=920621
Thanks for the ref.
--Chris
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
