# from Sisyphus
# on Sunday 24 September 2006 02:29 am:

>we have an XS file that we can bundle with
>a normal Makefile.PL, MANIFEST, etc and put on CPAN.

good points, but:

a) How much trouble is it to have a dependency on Inline::C ?

b) How do you make it clear that you want patches against your inline 
code and *not* the autogenerated XS?  (Or, is that not a big issue?)

c) What happens to the other perl code in the .pm file with "use 
Inline..." ?

Assuming you have good answers to those, I could see usefullness in 
something like "make xsdist" (and, "xs", "xstest" targets.)

Aside: I don't like the convention of changing the import() arguments in 
the .pm file (such as the "VERSION => ..." thing) to build a release.  
Mostly, it bothers me to have a diff in svn just because of a build.

>Anyway, I'm basically just trying to work out which way to go with
> this. Do I persevere with Inline::C2XS along its current lines ? or
> do I rewrite Inline::C2XS so that it use Inline::C to write the XS
> file ? or do I provide a patch to Inline/Inline::C ? or do I just
> forget about the whole issue ?

Without a compelling answer to (a), I would say "forget", but you may 
well have a compelling answer.

On another note, there was some interest in getting Module::Build to 
work with Inline.  I would personally prefer that, but a lot of the 
inline magic is in makefile generation, so a makeless implementation 
could be tricky.

As for patching Inline, I thought today might be a good day to again 
look at merging my changes onto http://svn.kwiki.org/ingy/Inline, but 
alas:  it is out to lunch.  Has anyone else looked at this lately?  It 
seems to have gone through some juggling around the beginning of the 
year, but without the benefit of a trunk, branches, tags layout.  Maybe 
something on svn.perl.org would be more reliable?

--Eric
-- 
"If you only know how to use a hammer, every problem begins to look like
a nail."
--Richard B. Johnson
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------

Reply via email to