Dan Sugalski:
# Okay, here are the milestones. Each is worth a point release. If we
# manage to take them in this order, great. :)
Rough dependency tree:
Arrays
Regular expressions (backreference storage)
Parser (probably)
Lexicals (probably, though could be a hash instead)
Hashes
Symbol tables
Method calls
Attributes
Per-object specials
Subroutines
Continuations
Method calls
Compiler
Optimizer
Get the picture? :^)
As far as regexen:
Since Apocalypse 5 on regexen is next up, I'd like comments
about what people would like to see in the next version of the engine.
I know Dan doesn't like the interface at all and believes that the best
route is compile to a bunch of ord() calls, I don't agree, and I'm
pretty sure I can beat ord. So, I'd like to know what people think of
the current engine and what they'd like to see in a new one. That way I
can start preparing for the Great Rewrite (or something like that).
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
#define private public
--Spotted in a C++ program just before a #include
