Dan Sugalski wrote:
What I'd like is for folks to take the next day or three to think of the things that they need parrot to do that aren't working or designed yet, and throw them at the list.
TODO:
- badly needed: line numbers in packfile (implying PBC extensions)
- run through KNOWN_ISSUES (which I updated not too long ago) and
make this file as short as before my update ;-)
- DOD with optimized parrot compile (mark processor regs) on $arch?
- Design documents e.g. vtable var/value split
I would like to have a docs/architectures.pod with all pecularities of all todo supported $arch's. Same would be fine for C-compilers.
Enough for now,
leo
