|parrotcode: A plan for parrot 1.0 and beyond.|
|Contents | Project Information|
ROADMAP - A plan for parrot 1.0 and beyond.
A high level overview of the work that is remaining to release parrot 1.0, including both user-visibile features and internals.
For detailed information regarding specific tasks, we will refer to https://rt.perl.org/rt3.
For a high level overview of funded parrot milestones for 1.0, please see: http://www.perlfoundation.org/parrot_grant_from_nlnet
This document also contains information about future direction after 1.0.
Each task is associated with a major release of parrot. Additionally, each task will refer to its current state, and a link to any documentation regarding the task (i.e. something on Launchpad, RT, or in the repository, or on the wiki). Tasks with no supporting documentation will be marked [Unspecifed].
While the 1.0 release must pass all of these quality goals, future releases will of course adhere to these standards as well.
Eliminate dead documentation. Let historians dig through our subversion history. We look forward toward successful deployment. -Chip
Parrot currently requires perl5 to build. Eventually we wish to eliminate this requirement.
The contents of this file are outdated and must be reviewed. See RT #48611. All content beyond this point needs to be validated.
The remaining tasks are broken down into the following categories, roughly listed in the order through which a task might progress.
[NOTE: this does not currently work. Why? --committer]".
PDDs are not exceptions to this rule! Fix them when they're wrong. Delete them when they're obsolete. (Never delete docs lightly, though. Check first with someone who should know.)
http://xrl.us/gvfw (Link to groups-beta.google.com)
Section 1 of that email needs a decision from the Architect.
(Note: Whatever tech we use to implement transcendental math should at *worst* compile to function calls under JIT. And I'll consider making exceptions for the transcendantal math if someone can show me why.)
I expect PIR will still let you pretend they're opcodes, though, to avoid immediate howls of outrage. (But only silicon-based life forms write PASM, so we're not worried about that.)
struct PMC_EXT. PDD04
[[What's an EDA? --Coke]]
loop: dec I0 inc I1 # or add, sub, ... if I0, loop
isn't handled correctly on JIT/i386.
Parrot_destroycurrently leaks most of the memory that it is supposed to free. embed.pod