At 2:31 AM -0500 1/9/03, Joseph F. Ryan wrote:
This sounds like a good idea, and one that'll make development easier while this compiler is still in use. Please, by all means implement the changes.Dan Sugalski wrote:Could one of the folks working on the perl 6 parser give us a status update as to where it stands? Which bits of the apocalypses don't work, and what parts of the regex definiton's not done yet? Things have stalled a bit, and I'd like to get it going again, and the perl 6 tests into the standard parrot test suite.
I think that before development kicks back up again, perhaps we use the long absense to look objectively at P6C and look for potential places to refactor. For instance, one thing that I'd like to do is abstract operator symbols from their node definition. After the monster operator thread on p6-lang awhile back, at least 50% (guess) of the operators are no longer the same as they used to be. However, these symbols are still hardcoded into the Binop node type, meaning that nearly every single module in P6C needs to be updated. However, if the symbols were mapped to an operator name/number in the tree deciphering phase in Tree.pm, then updating the operators would be simple if future changes occur.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
