Bryan C. Warnock:
# On Saturday 23 February 2002 23:20, Brent Dax wrote:
# > The Right Answer is probably to change all the STRING*s in
# the core to
# > Parrot_Strings. However, there are two problems with that:
#
# I think that's the recommended school of thought, although
# I've always
# preferred *not* to typedef the final pointer. It makes it a
# little clearer
# to me what I'm dealing with.
# >
# > -STRING* is supposed to be a way for core hackers to avoid
# extra typing.
# > While you're at it, why not s/INTVAL/Parrot_Int/g?
#
# Hey, I was happy with INT and UINT. And P instead of Parrot.
#
# That would make it a PINT. So a short would be a HALFPINT.
#
# > -That's a damn big change.
#
# And it can only get bigger.
The Magic Word in this case is "embedders".
a) We can't reserve "any symbol starting with 'P'" to Parrot. That's a
little too wide a scope.
b) I'd rather not have embedders worrying about "is this a value type or
a pointer type?". They don't *want* to learn about Parrot's internals,
they just want to *use* Parrot. Questions like "does this type have to
be declared as a pointer?" interfere with questions like "how should I
best write this parser?".
--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
