Class creation in bytecode
Dan Sugalski
since the metadata spec post, here's the equivalent for assembly. I'll
stub in and commit the stubbed object.ops ops in a bit.
We've already got ops to create a class standalone, and to subclass an
existing class. We're also going to add the following ops:
addparent Px, Py
removeparent Px, Py
To add and remove class Y as a parent of class X
addattrib Ix, Py, Sz
removeattrib Px, [IS]y
To add attribute Z to class Y. X gets the attribute offset. removeattrib
removes attribute #y or named Y (depending on whether it's a string or
int) from the class
To add or remove an implemented interface:
adddoes Px, Sy
removedoes Px, Sy
Instantiate, as implemented, is dead. I'm going to nuke it, then use it
for instantiating classes via metadata chunks. That's next message.
Dan
Matt Fowles
Dan Sugalski wrote:
> To add or remove an implemented interface:
>
> adddoes Px, Sy
> removedoes Px, Sy
>
> Instantiate, as implemented, is dead. I'm going to nuke it, then use it
> for instantiating classes via metadata chunks. That's next message.
Just a thought, but (add/remove)interface seems a little more
undetstandable...
Matt
PS-Dan, what happened to you sig? I rather liked it.
Dan Sugalski
> All~
>
> Dan Sugalski wrote:
> > To add or remove an implemented interface:
> >
> > adddoes Px, Sy
> > removedoes Px, Sy
> >
> > Instantiate, as implemented, is dead. I'm going to nuke it, then use it
> > for instantiating classes via metadata chunks. That's next message.
>
> Just a thought, but (add/remove)interface seems a little more
> undetstandable...
I can see it going either way, but this is shorter and it amuses me some,
so it's good enough. :) It only matters for hand-written assembly.
> PS-Dan, what happened to you sig? I rather liked it.
It only pops up when I'm using Eudora. I've been using Pine for the most
part the past few weeks. Probably ought to get it moved over.
Dan