We've all been pretty good about things so far, but I do want to remind
folks to take a look at the bigger picture when they're deciding on
features (or mis-features... :) of Parrot.
First, and most importantly, the following should be considered "cast in
stone" things. (In the long run, *not* at the moment)
* On-disk bytecode files
* Documented public APIs for embedders and extension writers
* The assembly language
Or, basically, anything in a PDD.
Things that are *not* cast in stone:
* All the source
So, while critiques of the source as it currently stands are *very* welcome
(no, really, they are!), it's best to not assume that the final interpreter
will use the code you think is nasty now. (Of course, pointing out (and
fixing, though that's optional) the problems helps fix them)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
