Dan Sugalski:
# At 8:10 PM -0800 2/23/02, Brent Dax wrote:
# > typedef struct foo_t * FooPtr;
# > typedef struct foo_t FOO;
#
# Y'know, thinking about this, I don't like this trick. That should be
# FOO, and FOO *.
#
# We either typedef the struct, or the pointer to a struct. Not both.
Different scopes, different policies. Outside the core (and in places
with external visibility) we use the Parrot_Foo-type pointer-to stuff;
inside we use FOO. *This is the same policy we have now*, except for
the outside the core part. I want that because I want to present a
unified, simple interface to embedders so they don't have to sweat the
small details. I *really* don't want their program to not work because
they typed "Parrot_String" instead of "Parrot_String *".
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking, regex hacker, embedding coder, and boy genius
#define private public
--Spotted in a C++ program just before a #include
