----- Original Message -----
From: "Jerome Quelin" <jque...@gmail.com>
To: "Sisyphus" <sisyph...@optusnet.com.au>
Cc: "David Oswald" <daosw...@gmail.com>; <inline@perl.org>
Sent: Monday, December 05, 2011 9:10 PM
Subject: Re: Strategy for improving install success of Inline::CPP
hi,
On 11/12/05 20:37 +1100, Sisyphus wrote:
In all seriousness, this probably should have been addressed some
time ago - thanks again, Patrick, for writing the patch.
And thanks, David, for raising the matter.
great! as inline::befunge author, i also get lots of errors due to the
fact that befunge isn't registered as inline backend...
i raised the question quite some time ago (a looong time), but since it
wasn't solved i just left it as is - that is, with tests failing.
Good things come to those who wait ;-)))
(But I'm sorry it has taken so long.)
so, to solve the problem, does it mean we just have to:
- require inline 0.49 (when it's available out there)
Yep - that's it :-)
- change tests from:
use Inline "Befunge";
to:
use Inline Config => _TESTING => 1;
No, you shouldn't need to specify that config option. You can just leave it
as simply:
use Inline "Befunge";
use Inline "Befunge";
- will there be sthg else to do?
Nope - if we've got it right that's all you need to do.
And please let us know if you still get cpan tester reports that include
that M19_usage_language failure.
Cheers,
Rob
