Dan Sugalski [EMAIL PROTECTED] writes:
At 11:13 AM +0100 12/14/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
subclass - To create a subclass of a class object
Is existing and used.
Right. I was listing the things we need in the protocol. Some of them
we've got,
Dan Sugalski [EMAIL PROTECTED] wrote:
subclass - To create a subclass of a class object
Is existing and used.
add_parent - To add a parent to the class this is invoked on
become_parent - Called on the class passed as a parameter to add_parent
What is the latter used for?
At 11:13 AM +0100 12/14/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
subclass - To create a subclass of a class object
Is existing and used.
Right. I was listing the things we need in the protocol. Some of them
we've got, some we don't, and some of the stuff we have we
Dan Sugalski [EMAIL PROTECTED] wrote:
Now, there is one big gotcha here -- multimethod dispatch. I'm not
entirely sure that we can do this properly and still give classes
full control over how methods are looked for and where they go.
Thinking about MMD a bit more, I can imagine the following
Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
Anyway, so much for the 'outside world' view of objects as black box
things that have properties and methods.
[ ... ]
Almost everything we do here is going to be with method calls.
There's very little that I can see that requires any
Right, so with at least a basic rework of the string stuff in, it's
time to turn our attention to objects and all the stuff that goes
with them.
I'd originally thought that the bits we'd put in place would be
sufficient to do everyone's object system (well, all the languages
that we
