Dan Sugalski:
# At 8:35 PM -0800 2/23/02, Brent Dax wrote:
# >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?".
#
# This doesn't hold. The types we expose to embedders don't have to be,
# and probably shouldn't be, what we have internally. The namespaces
# and exposed types should be separate.
That'll just give us an explosion of wrapper types. Like it or not,
embedders (and extenders--don't forget about them) will need to do some
simple operations on PMCs and strings. We need to accommodate that.
--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
