Shouldn't {g,s}etattribute opcodes call vtable methods of the object?
Well... no, not really. There's no need for this as such. Properties are on the PMC as a whole, so you really don't have any idea what the structure of the PMC is. Attributes are all class-specific and the class code *does* have deep knowledge of the structure of the object, at least at the moment.
At some point we'll need to see about some generalized structure--maybe. It depends a lot on whether anyone actually cares or not. I can see a big "not" here, in which case vtable-ing the things won't buy us anything but a performance hit.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
