Changes between Version 4 and Version 5 of PirateTodo

Timestamp:

01/08/11 02:23:31 (11 years ago)

Author:

bacek

Comment:

Wiki-syntax fix

PirateTodo

@@ -3 +3 @@
 This should be an approximately ordered list of what's necessary to bring PIRATE to completion as Parrot's default PIR compiler.
 
-* ~~fix examples/pir/make_hello_world_pbc.pir for a post-dynop_mapping parrot~~
+ * ~~fix examples/pir/make_hello_world_pbc.pir for a post-dynop_mapping parrot~~
   - ~~OpLib needs to be made aware of op mapping.~~
   - ~~We need a dedicated PackfileBytecodeSegment PMC to hold the op mapping (and generally be less hacky than a raw segment).~~
   - ~~this code serves as a minimal test case for the feasibility of our packfile PMCs for pbc generation.~~
-* Update nqp-rx to use PIRATE's POST format.
+ * Update nqp-rx to use PIRATE's POST format.
   - the current version uses strings rather than structure to store data and isn't amenable to PBC generation without a full PIR compiler
   - some discussion with pmichaud is necessary, but he supports the change
   - this is necessary to enable direct POST->pbc translation and by extension, POST->pbc->Lorito translation
-* Move PIRATE to compilers/ and make it optional as Parrot's default PIR compiler.
+ * Move PIRATE to compilers/ and make it optional as Parrot's default PIR compiler.
 
-* Make Parrot's build work and tests pass with PIRATE as the PIR compiler.
+ * Make Parrot's build work and tests pass with PIRATE as the PIR compiler.
   - Do the same for Rakudo, Partcl and any other HLLs and libraries that are actively maintained at the time.
-* Rip out imcc ~~and delete pirc~~.
+ * Rip out imcc ~~and delete pirc~~.
   - A post-imcc party is optional but highly recommended.
-* Make PIRATE output Lorito ops (or a LOST tree) based on PIR->Lorito translations.
+ * Make PIRATE output Lorito ops (or a LOST tree) based on PIR->Lorito translations.
   - Once this happens, we can use the Lorito to generate C code for a byte-code free bootstrapping build.