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?
Same thing. The difference is a result of my lousy memory and lack of research.
2) B<classoffset> isn't really needed.
set I0, PClass["attr"]
exists and is working
Pretty much all of the current object stuff is getting yanked out and replaced. It's first draft and needs redoing.
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?
That was specified in the PDD. *If* a class is looking up by name, something it generally won't do, it uses the fully-qualified name of the attribute, in the format that the class wants. Since a class is soley responsible for its naming scheme this should be reasonably safe.
Please have a look at t/pmc/obj*.t for the current state.
Those'll need to be redone as well. Something for later, when the spec is done. -- Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
