/ 
parrot-0.8.1
/ ROADMAP

NAME

ROADMAP - A plan for parrot 1.0 and beyond.

OTHER DOCUMENTS

See https://trac.parrot.org/parrot/wiki/ParrotRoadmap, created at the Parrot Developer Summit in November 2008.

PURPOSE

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.

LAYOUT

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].

1.0

Features

TBD

Quality

While the 1.0 release must pass all of these quality goals, future releases will of course adhere to these standards as well.

  • All known GC bugs must be resolved

  • All known segfaults must be resolved

  • All features must have comprehensive tests

  • All features must have comprehensive documentation

  • All tests must pass on all core platforms

  • Remove obsolete code/documentation.

    Eliminate dead documentation. Let historians dig through our subversion history. We look forward toward successful deployment. -Chip

2.0

Build System

  • Eliminate perl5 build requirement. [Unspecified]

    Parrot currently requires perl5 to build. Eventually we wish to eliminate this requirement.

UNREVIEWED CONTENT

The contents of this file are outdated and must be reviewed. See RT #48611. All content beyond this point needs to be validated.

OVERVIEW

The remaining tasks are broken down into the following categories, roughly listed in the order through which a task might progress.

DOCUMENTATION

  • When docs and code disagree, they must be brought into agreement immediately. At the very least, appropriately mark docs that are apparently wrong but may eventually become right, e.g.: "[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.)

  • Document project goals and priorities.

DESIGN

  • MMD Roundup 2, from the mailing list:

    http://xrl.us/gvfw (Link to groups-beta.google.com)

    Section 1 of that email needs a decision from the Architect.

  • Design the standard library to replace all those opcodes that should never have been opcodes in the first place, e.g. the IO and transcendental math features.

    (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.)

  • Finish event and IO specification.

  • Finish specification of return continuation and sub being called slots in interpreter, with introspection

  • Spec out bytecode metadata system and introspection/modification system

  • Specify what we need to serialize continuations

  • Solidify design for Truly Evil speed hack for fast regex/string matching

  • Describe the behavior of the serialization functions. (freeze, thaw, thawfinish, visit). PDD02

  • Describe the behavior of share. PDD02

  • Describe the components of a struct PMC_EXT. PDD04

  • Define what bits of the Parrot internals should be exposed as part of the Parrot API for extension writers.

TODO

  • IO: Add IO tables, right now IO's just float around.

  • Finish PMC for IO object

  • IO's "stdio" layer: buffering, seek/random access, shared streams, thread safe

  • Copy-on-write IO stacks

  • Make IO layer cache the vtable calls to the next layer.

  • IO Filters

  • IO mmap support

  • Bottom level socket/pipe/process support in API

  • UTF layers (or should we not bother and do as a filter?)

  • Sample programs and test suite

  • AIO - On many platforms we must fake async IO, are we doing a background thread/interp or an inline event queue function that is called every N ops?

  • Get digest (probably SHA1) added to bytecode segments

  • Speed up the OrderedHash implementation

  • Rearchitect internals for the string specifications.

  • To PerlClass or not to PerlClass, that is the question. The class hierarchy should be reworked (e.g. Boolean->PerlInt->Scalar).

  • Configuration - missing tests for processor features

  • Configuration - duplication, e.g. nvsize/numvalsize

  • IO - Async core isn't there yet, even though it is rumoured to be.

  • Overflow detection/promotion to bigint/float types.

  • Fill in the remaining functions from the EDA, verify that the test suite still passes, integrate the library into the rest of Parrot, provide PMC types and suitable opcodes. Conversion to and from Parrot strings, conversion to and from floating point types, sprintf output of bignumbers. PDD14

    [[What's an EDA? --Coke]]

  • TODO - rewrite debugger.

BUGFIX

  • You can add parents to a class with children and objects, and attributes to a class with children or objects. This is silently allowed and quietly corrupts the child classes and instantiated objects.

  • building miniparrot is broken

  • GC issue (copying collector) - immobile strings/buffers get freed during GC.

  • Memory leak - PIO subsystem leaks file handles (ParrotIO structures)

  • Memory leak - string_to_cstring returns a malloced string, which isn't freed everywhere

  • Memory Leaks - imcc is currently leaking Unit structures and possibly more

  • JIT - 64 bit integers on 32 bit machines don't work

  • JIT - parrot register inspection is incomplete (P-regs)

  • This sequence:

    loop: dec I0
      inc I1       # or add, sub, ...
      if I0, loop

    isn't handled correctly on JIT/i386.

  • Parrot_destroy currently leaks most of the memory that it is supposed to free. embed.pod

PORTABILITY

  • Portable fcntl() replacement for platforms without it

  • See pdds/draft/pdd01_overview.pod. Test suite should have no failure on supported platforms.

  • Tests - src/tests are not supported on all platforms

  • ParrotIO uses integral file descriptors, which may not be portable. src/ops/io.ops

  • conversion ops for machines without 1/2/4 byte integer data types

  • 32 bit pointer/64 bit integer and vv.

  • dynamic library loading