Bryan C. Warnock:
# On Friday 22 March 2002 18:05, Brent Dax wrote:
# > Russ Allbery:
# > # Brent Dax <[EMAIL PROTECTED]> writes:
# > # > Parrot_Foo for external names, FOO for internal names, struct
# > # > parrot_foo_t for struct names.
# > #
# > # POSIX reserves all types ending in _t. I'm not sure that
# extends to
# > # struct tags, but it may still be better to use _s or
# something else
# > # instead to avoid potential problems.
# >
# > My understanding is that it only reserves types that start
# with 'int' or
# > 'uint' and end with '_t'. You might wanna check that, though...
#
# wchar_t, size_t, off_t, dirent_t, pid_t, uid_t, gid_t, socklen_t, etc.
# Dunno how many are actually POSIX, but....
#
# >
# > Besides, what's the probability it'll be a problem if we prefix all
# > struct names with 'parrot_'?
#
# You don't really want to do that, do you?
Yes, in fact, I do. In the general case, you will never have to use the
'struct' name--inside the core you'll use String or PMC or whatever, and
outside you'll use Parrot_String or Parrot_PMC or whatever.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#define private public
--Spotted in a C++ program just before a #include
