Hey David - Looking over the perl-xs mailing list history, I see somebody inquiring about C++ and XS, with a suggestion to look at this: p3rl.org/ExtUtils::XSpp
I'm not suggesting that you switch over to using EU::XSpp, but I thought the additional point of reference might be helpful. Perhaps adding a link in the See Also section would be good, too. David On Fri, Feb 24, 2012 at 3:51 AM, Sisyphus <sisyph...@optusnet.com.au> wrote: > > ----- Original Message ----- From: "David Oswald" <daosw...@gmail.com> > To: <perl-xs@perl.org> > Cc: <inl...@perl.org> > Sent: Friday, February 24, 2012 7:01 PM > Subject: ExtUtils::ParseXS can generate invalid C++ > > > > [ This message is being sent to perl-xs@perl.org seeking suggestions, >> with a CC to inl...@perl.org as an FYI. ] >> >> We have a situation with Inline::CPP wherein the module is failing to >> pass smoke testing when the compiler is g++ version 4.4.3 (though I >> think the issue probably goes back to 4.2.1). Here is an example of >> two failure reports: >> >> http://www.cpantesters.org/**cpan/report/35702916-59fc-** >> 11e1-8417-42773f40e7b5<http://www.cpantesters.org/cpan/report/35702916-59fc-11e1-8417-42773f40e7b5> >> > > Can't reproduce the problem. > I've tried gcc versions 4.7.0, 4.5.2, 4.4.7, and 4.4.3 on various builds > of perl (all on MS Windows). > > In each case I was building 0.34_002, with Inline-0.50_01 and > Parse-RecDescent-1.67006 - same as the above tester. > > I reckon I've seen similar before, and just assumed it must be the result > of some locale setting. > > Cheers, > Rob > -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan
