>>This works as long as people (a) know of (b) stick to the policy
>>("Interp for internal use only") (c) No application embedding Parrot
>>has defined "Interp" themselves. Experience has shown that none of
>>these is likely to happen and/or stay that way for long :-)
>
>
> (c) is the reason for the separate embed.h file that doesn't actually
> include any other parrot header files--that cuts down on our exposure
That sounds good. But I won't be surprised if in some platform even
that isn't enough :-)
> to other headers that parrot uses internally. I'm not naive enough to
> think that makes us immune to problems, but at least it reduces our
> exposure. :)
