#12: Task list for completing PIRC
--------------------+-------------------------------------------------------
 Reporter:  kjs     |       Owner:  kjs 
     Type:  todo    |      Status:  new 
 Priority:  normal  |   Milestone:      
Component:  pirc    |     Version:      
 Severity:  none    |    Keywords:  pirc
     Lang:          |       Patch:      
 Platform:  all     |  
--------------------+-------------------------------------------------------
Description changed by kjs:

Old description:

> Task list can be found in compilers/pirc/TODO, and includes:
>
> 1.  Emit the actual bytecodes into a PackFile/codesegment.
>
> 2.  Create a PMC constant for strings, numbers, keys and
>     subroutines.
>
> 3.  Complete PASM output, so it can actually be parsed and run.
>
> 4.  Handle :multi flag properly.
>
> 5.  Handle nested macro expansions.
>
> 6.  Fix all memory leaks. this should be trivial, given PIR's built-in
>     allocated-memory-pointer-registering infrastructure. In some
>     places this is not used yet, and in others, it's not necessary
>     to use it (but in those mem_sys_free() must be called explicitly).
>
> 7.  Figure out how :named argument passing works in bytecode.
>
> 8.  Finish the parrot calling conventions ops in the back-end
>     (var.args must be fixed).
>

> This is a tracking ticket.

New description:

 Task list can be found in compilers/pirc/TODO, and includes:

 1.  Emit the actual bytecodes into a PackFile/codesegment.
 This is done.

 2.  Create a PMC constant for strings, numbers, keys and
     subroutines.
 Strings, numbers and subs are stored.
 Keys still todo.

 3.  Complete PASM output, so it can actually be parsed and run.
 TODO

 4.  Handle :multi flag properly.
 TODO

 5.  Handle nested macro expansions.
 TODO

 6.  Fix all memory leaks. this should be trivial, given PIR's built-in
     allocated-memory-pointer-registering infrastructure. In some
     places this is not used yet, and in others, it's not necessary
     to use it (but in those mem_sys_free() must be called explicitly).
 TODO

 7.  Figure out how :named argument passing works in bytecode.
 TODO

 8.  Finish the parrot calling conventions ops in the back-end
     (var.args must be fixed).
 DONE.

 This is a tracking ticket.

--

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/12#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to