On Mon, Dec 10, 2007 at 04:37:31PM +0200, Allison Randal wrote:
> Tim Bunce wrote:
>
> >> 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.
> 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.)
> Sounds good.
I added a tool to check the coverage of the embed.h API:
$ perl tools/check_embed_coverage.pl ../../include/parrot/embed.h Embed.xs
20 out of 25 Parrot_* functions in ../../include/parrot/embed.h not used in
Embed.xs:
Parrot_clear_debug
Parrot_clear_flag
Parrot_clear_trace
Parrot_debug
Parrot_disassemble
Parrot_exit
Parrot_init_stacktop
Parrot_run_native
Parrot_runcode
Parrot_set_config_hash
Parrot_set_debug
Parrot_set_flag
Parrot_set_run_core
Parrot_set_trace
Parrot_setup_argv
Parrot_setup_opt
Parrot_setwarnings
Parrot_test_debug
Parrot_test_flag
Parrot_test_trace
I'd appreciate some guidance on what interfaces are most stable / least
likely to change / most useful so I can prioritise my time.
Similarly it may help Jeff prioritise work on PDD10 as more spec detail
would help me write some tests.
>> 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.)
So should I just delete the Build related files?
Tim.
