Opcode and OpLib PMCs

Andrew Whitworth wknight8111 at gmail.com
Thu Feb 11 21:38:16 UTC 2010

They're pretty bare-bones for now, mostly serve to convert op name to
opnumber and vice versa. I'll put up some example tests later and we
can grow from there.

--Andrew Whitworth

On Thu, Feb 11, 2010 at 4:14 PM, Jonathan Leto <jaleto at gmail.com> wrote:
> Howdy,
> Are there any tests that you would like to be written for these? If
> you push me in the right direction I can add some test coverage and
> get to know how they work at the same time.
> Duke
> On Thu, Feb 11, 2010 at 12:14 PM, Andrew Whitworth
> <wknight8111 at gmail.com> wrote:
>> I've created two new prototype PMCs in the op_pmcs branch: Opcode and
>> OpLib. OpLib is a singleton that provides access to the interp->op_lib
>> structure and acts like a factory for Opcode PMCs. Opcode PMCs
>> represent a single opcode and can be used to get information about
>> them, most importantly the op number so we can start looking at the
>> possibility of doing bytecode compilation from PIR.
>> These PMCs are bare bones now. They obviously need some feature
>> additions and other maturation, but I would like to get some eyes on
>> them and some comments/suggestions from people so these can grow in a
>> good way.
>> --Andrew Whitworth
>> _______________________________________________
>> http://lists.parrot.org/mailman/listinfo/parrot-dev
> --
> Jonathan "Duke" Leto
> jonathan at leto.net
> http://leto.net

More information about the parrot-dev mailing list