Tim Bunce wrote:
I'm interested in doing some work on Parrot::Embed.
Great!
So I'm wondering what state it's in and if there are any short term
plans for it.
Any good reason it's not part of the normal build/test cycle?
Only that it's incomplete.
Also, what's the status of docs/embed.pod? It seems out of date and/or
imcomplete (no mention of Parrot_call_sub, for example).
>> I meant docs/pdds/draft/pdd10_embedding.pod
>>
>> I could trying hacking on it to at least mention all the functions
in embed.h
>> with a few words on each. I'd be fumbling in the dark mostly but it
would at
>> least push the document along for others to review later.
This was a partial first draft written by chromatic. The
extending/embedding PDD's aren't on the core list of milestones, so I
don't have a specific date when I'm planning to work on it. It probably
makes the most sense to repeat the group drafting strategy we're using
with the PIR PDD. You and others can help pull together the draft PDD,
and I'll review/revise/approve it as it reaches a relatively solid
state. We can also also talk back and forth about ideas on the mailing
list as it solidifies.
There are two parts of the group drafting task: documenting how the
system works now, and documenting how you would like it to work.
Documenting the functions in embed.h is a great place to start.
I'm very much a novice with parrot. So my preferred approach for now
would be for someone more knowledgeable (Allison, chromatic, ...)
to lead the way by updating/expanding the docs/embed.pod specification.
At the moment, chromatic or I would start exactly where you'll be
starting: sitting down with the code, extracting a list of current
functions/features, and at the same time keeping an eye out for missing
features, misfeatures, or other places in need of improvement. So, if
you or others are willing to take a first stab at it, it would be
enormously helpful. (It's also a great way to gain experience with parrot.)
I'll update/expand Parrot::Embed in sync and address the items in the
TODO file along the way. Sound okay?
Sounds good.
Meanwhile there's some housekeeping I can be getting on with.
Like fixing the broken Makefile.PL (seems best to make it a wrapper for
the working Build.PL)
Actually, what we'd like to do is eliminate the Module::Build
dependency, and integrate the build process for Parrot::Embed into
Parrot's build process (which is all Makefiles).
chromatic wrote Parrot::Embed as an independent CPAN module, but with
the need to always have a version of Parrot::Embed that's compatible
with the version of Parrot you have installed, we'll ship them together.
(It may also be dual-life'd on CPAN, that's one of the open design
questions.)
Allison
