At 10:14 AM -0500 1/25/02, Andy Dougherty wrote:
>One problem noted recently on the p5p list is that if you do
>
> #include <perl.h>
>
>in your program, it exposes a *lot* of CPP #defines to your program,
>whether you want them or not. This is particularly a problem if you wish
>to embed perl or use it with an extensive 3rd-party library.
>
>For parrot, we'd ideally like to make it a lot safer to
>
> #include <parrot/parrot.h>
Nope--we'd ideally like to smack anyone writing non-core code that
does that. :)
Embedders will include parrot/parrot_embed.h, while extension folks
will include parrot/parrot_extend.h. Neither will include
parrot/parrot.h--not safe.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
