"B. K. Oxley (binkley) at Home" wrote:
>
> Brian Ingerson wrote:
> >
> > 1) 'perl -MInline=makedist' to generate a CPAN distribution (using a
> > MANIFEST).
> > 2) 'perl -MInline=makeppd' to generate a pre-compiled, binary
> > distribution.
> > 3) 'perl -MInline=makeppd,nosource' to make a binary-only
> > (source-stripped) distribution.
>
> This is all great! But how is it specific to Inline? Shouldn't it be
> part of ExtUtils?
I see your point, but step back for a moment.
Inline *is* the new ExtUtils! :)
I don't mean to sound arrogant. But if Inline can completely replace XS,
why not have it replace the existing related tools. When I say "replace"
I mean "abstract". Inline always makes use of existing tools behind the
scenes but strives to make the user interface as simple as possible.
One of the current advantages of not having Inline in the core, is that
we can make these tools work equally well back to 5.005_03. Changes to
ExtUtils could only reasonably be made for 5.7.1+. And it would require
interaction with P5P (which my current schedule does not permit ;)
So in a way its all just a matter of packaging.
The above command syntax could be rewired to look like:
makedist
makeppd
makeppd --nosource
These should still probably ship with Inline so that they are Inline
aware, and kept in sync. But they could be used for pure perl as well.
Thanks for getting me thinking!
Cheers, Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
