Okay, I got a little further. Along the way, various issues of varying potential to make me really sick came up. Supposing I release Module::Inline::C to CPAN, here's the recipe for converting your Inline::C-based CPAN distribution to use Module::Inline::C. This works for MakeMaker-based distributions only at this point.

• Replace all invocations of Inline with M::I::C:

  # use Inline C => '<<HERE';
  # becomes
  use Module::Inline::C <<'HERE';
  ...
  HERE
  [download]

• Replace the 1; that ends the module/.pm file with use Module::Inline::C 'END';
• The version declaration of your module needs to be accessible at compile time and also determinable by MakeMaker which uses a simple regex to extract it. That means you need to do this:

  # our $VERSION = '0.01';
  # becomes
  our $VERSION = '0.01';
  BEGIN {$VERSION = '0.01'};
  [download]

  (Similarly if you prefer use vars '$VERSION'.)
• You need to add a bit to your Makefile.PL. For module Foo::Bar, this might look like:

  use ExtUtils::MakeMaker;
  
  my $module_file = 'lib/Foo/Bar.pm';
  WriteMakefile(
      NAME              => 'Foo::Bar',
      VERSION_FROM      => $module_file,
      PREREQ_PM         => {
         'Module::Inline::C' => '0', # instead of Inline
      },
      ($] >= 5.005 ?
        (ABSTRACT_FROM  => $module_file,
         AUTHOR         => 'Your Name <and@e.mail>') : ()),
      dist => {
          PREOP => "perl -MModule::Inline::C::MM=\$(DISTNAME)-\$(VERSION
  +) -c $module_file",
      },
  );
  [download]

  The dist => ... part specifies that before tar-ing up the distribution file, the Inline::C to XS conversion should take place. The MANIFEST of the generated distribution is updated automatically.

That should be mostly it. Afterwards, anybody downloading and installing your distribution should be able to do the usual

perl Makefile.PL
make # compiles XS => so/dll into blib/
make test # doesn't use Inline!
make install # no more Inline for this module, ever.
[download]

Of course, the user is free to delete the .xs files from the distribution and use Inline instead. Using Inline::C can be much more enjoyable for development (IMHO).

There's still a lot of cleaning up to do as well as adding documentation and implementations for Module::Build and Module::Install. Additionally, if you have a distribution with several XS (or rather: Inline::C) modules, you might run into trouble with this. But you're welcome to read up on the issue. It's not specific to this but rather common to all XS distributions.

Steffen

Update: I forgot one item in the list.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.