C++ automatically generates a typedef name when it sees struct Foo { .. }
We have a few places that name the typedef with the same name
as the tag (which I don't like as style anyway), and its causing problems
when trying to compile a C++ extension lib with parrot headers.One example: interpreter.h struct Parrot_Interp; typedef struct Parrot_Interp *Parrot_Interp; This is fine for C but many people writing extensions won't be using C. -Melvin
