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.
great to see this, i guess everyone will agree. well, i have some questions...
what i couldn't find is how to register a method address and name with a class,
so that fetchmethod will return it? am i looking in the wrong place?
Not gotten there yet. :)
By default methods are in class namespaces, so fetchmethod would (by default, mind) just look in each class namespace in the parent array for the method until it finds one. We're going to provide method caches, since otherwise performance will really suck, but that's an optimiziation.
the instantiate opcode takes 'metadata' as its second argument. how is this supposed to be constructed and when is this method of creating a new class appropriate instead of newclass and subclass ops?
I was wondering if someone'd catch that. The metadata stuff is entirely unspecified, but it's in there for later. (Or, rather, not-quite-now) It's to be used in the case where you have all the info for a class at instantiation time and want to be able to say "make me a class with parents X, Y, and Z, and eighteen attributes with these names" and do it in one go, rather than as a series of addparent and addattribute ops.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
