Dan Sugalski <[EMAIL PROTECTED]> wrote:
> While I'm still working on the vtable and supporting code section,
> most of the revamp of PDD15 (objects!) is checked into the
> repository. It'd be worth checking it out and checking it out, as
> this would be the time to get comments in.
1) Why is the existing opcode B<find_method> now B<fetchmethod>? Or do
they different things?
2) B<classoffset> isn't really needed.
set I0, PClass["attr"]
exists and is working
3) The same holds for B<setattr> and B<getattr>
set PObj["attr"], Pattr
set PObj[0], Pattr
are implemented and working. *And* this syntax allows also
set PObj[0], 42 # set attr #0 from constant
set PObj["answer"], 42
The B<{g,s}etattr> are only allowing PMC attribute values.
Now we could of course say that B<getattr> is somewhat more descriptive
then the keyed access. OTOH the keyed access matches perl5s blessed ref
of array or hash syntax and avoids increased opcode count (the more, if
native types are to be handled too).
And finally - I asked that already a few times - how does B<"attr">
above really look like? Is this a full qualified name? Or only when two
classes have the same attribute?
Please have a look at t/pmc/obj*.t for the current state.
leo
