Erk, we seem to be muddling around in that great grey area between what is
Parrot and what is Perl.
Parrot is striving to be a common backend for multiple scripting languages,
of which one is Perl 6, no? And, of course, to adequately test Parrot, you
need to concurrently develop Perl 6, yes? And that is what is currently
happening, yes? No. (At least, it doesn't seem so.)
Certainly, register creation, memory allocation, garbage collection, and
opcode dispatch are definitely within the purview of Parrot. However, the
opcodes' code themselves aren't - they're provided by the language.
Of course, some concepts are global across multiple languages, so where *do*
those commonalities lie? Are those things part of a Parrot sublanguage that
all superlanguages are expected to build on top of?
Parrot may provide facilities for vtable dispatch and string handling, but a
language isn't roped into using them.
Things to keep in mind. (And another reason why it's good to have Namespace
Police.... :)
--
Bryan C. Warnock
[EMAIL PROTECTED]
