Bryan C. Warnock:
# On Friday 22 March 2002 10:07, Brent Dax wrote:
# > Bryan C. Warnock:
# > # We're still all over the place with typedef name formats.
# > # We've FOO, Foo,
# > # and foo_t. We tried to hash this out before, but we didn't
# > # come to a clear
# > # consensus. (We got sidetracked by typedeffing pointers
# to typedefs.)
# > #
# > # What's it going to be?
# >
# > Parrot_Foo for external names, FOO for internal names, struct
# > parrot_foo_t for struct names. Now let's argue about if
# Parrot_Foo is
# > typedefed as a pointer or not. ;^)
#
# Oy vay!, none of which match PDD 07.
I don't think PDD7 took embedding into consideration.
# Shall we add parrot_foo_e for enums? (Which I'd actually
# like to do, if
# we're going to be that varied.)
Maybe. Ask Dan.
# Is Parrot_Foo strictly for external use - ie, there shouldn't
# be any use
# within the core?
I suppose you could use it in the core, but you wouldn't want to--the
internal names are there because they're shorter.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#define private public
--Spotted in a C++ program just before a #include
