Sam Ruby <[EMAIL PROTECTED]> wrote:
> Yes, I meant the ability to do things like '$P0 = new "Py_int"'.
> Could this be JITed? The mapping between string class name and assigned
> PMC type is constant throughout the life of the VM...
Not really or not easily. Fastest is to have type enum numbers
Leopold Toetsch wrote:
Sam Ruby <[EMAIL PROTECTED]> wrote:
I'm now converting to dynclasses. To be honest, I'm not thrilled with
this. What I would really prefer is a Parrot_new_p_s opcode with the
runtime worrying about caching class names across sub and module boundaries.
$P0 = new "Py_int"
o
Sam Ruby <[EMAIL PROTECTED]> wrote:
> I'm now converting to dynclasses. To be honest, I'm not thrilled with
> this. What I would really prefer is a Parrot_new_p_s opcode with the
> runtime worrying about caching class names across sub and module boundaries.
$P0 = new "Py_int"
or some such ha
By creating python specific PMCs, I got the pirate tests to pass, where
pass is defined as producing the exact same output as CPython produces
with the same input files.
These python specific pmcs were initally clones of perl specific PMCs,
with just enough added functionality (example: repr me
