Brent 'Dax' Royal-Gordon wrote:
Dan Sugalski wrote:
I hope it's not in there in the first place. The prefix needs to stay.
The declaration has been (along the lines of)
typedef struct Parrot_Interp { ... } Interp;
for years. The Interp typedef is intended for internal use only. Why do we need the prefix on an internal-use only typedef? We don't use Parrot_String or Parrot_PMC internally.
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 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. :)
--
Dan
--------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk