Patrick R. Michaud wrote: > On Sun, Jul 13, 2008 at 01:30:27PM -0700, Moritz Lenz wrote: >> I read ROADMAP again the other day, and thought about topics that we >> could offer new hackers to work on, hopefully mostly independent of >> other items in the roadmap. >> >> I didn't come up with something good, but instead I noticed a few things >> that I think should be added to the ROADMAP: > > Excellent. However, many of them require significant changes/improvements > to Parrot guts, as opposed to simply hacking on Rakudo itself.
I assume that's why they belong into the ROADMAP ;-) > So, here's > my categorization: > > Things requiring significant Parrot improvements or changes: > * concurrency > * Unicode string handling (different Unicode levels) > * custom meta classes > * parameter passing > > Things that may not require significant Parrot changes, but > still require a some (perhaps much) C programming: > * low level types > * pseudo packages (MY, OUR, OUTER, CALLER, CONTEXT, ...) > * perl 5 bridge > > Things that are awaiting substantial changes to the grammar engine > and grammar (which I plan to do over the next 2-3 months): > * various quoting syntaxes (q:stuff[...], <<...>>) > * Accessing operators via canonical name: my $x = infix:<+>(2, 3); > * operator overloading > * reduce and hyper metaoperators > > Things that require coordination with Parrot designers and other > HLL implementors: > * load libraries from other high level languages > * exceptions (die, fail, CATCH) > * warnings (waiting on exceptions to be finished) > > Things that are fairly simply implemented but just need some > design work: > * regexes: modifiers, substitution > * "no strict" > > It would probably be good to add the above to the ROADMAP, though. > I'm looking for a way to be able to annotate each item with its > completion status and/or dependencies -- I'm thinking perhaps > a set of "footnotes" for each item, such as > > * operator overloading [1,3] > * reduce and hyper metaoperators [1,2,3] > > 1. Awaiting PGE refactoring for protoregexes > 2. Awaiting longest token matching > 2. Awaiting STD.pm alignment > > > Comments? +1 Or maybe even enumerate the roadmap entries, and then use these to list interdepencies (for example numbers for entries and letters for footnotes). -- Moritz Lenz http://moritz.faui2k3.org/ | http://perl-6.de/
