Hi all,
I've held off on adding Parrot::Embed to the Parrot repository, pending
satisfactory answers to a few questions. I have ideas, but I'd really love
to get input from any or all of Bernhard, Jerry, Will, Leo, and Chip. This
one's a bit weird, so I want to disrupt life as little as possible.
* Where should the raw Parrot::Embed code go? It's not pure-Perl; it has an
XS component that needs building.
* What's the best way to integrate building this module from the main
Makefile? Should it be part of that process?
* Where should the built module go, and how can we make that work in a
cross-platform way? Copying the two (for now) necessary files out of
blib/lib appropriately is probably the right answer.
* Parrot::Embed uses Module::Build, mostly because I find EU::MM bletcherous
and hateful. Porting it to EU::MM is pretty easy, but I haven't done it
because it needs a custom step before testing to build a PBC file. Leaving
it as it is makes maintaining it a little easier for me, but it makes M::B a
dependency for building Parrot. That may or may not be an issue, depending
on what Bundle::Parrot pulls in.
* All of these questions assume that Parrot::Embed *should* go into the
repository. I think it's cool and useful and it lets us use
Parrot::Test::Embedded, which exercises the embedding interface with more
realistic code and hopefully speeds up and cleans up the test suite somewhat.
That may be insufficient reason, but it's what I have right now.
* Should this be a dual-lived module on the CPAN?
The source hasn't changed much since my last snapshot:
http://wgz.org/chromatic/perl/Parrot-Embed.tar.gz
-- c
