Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!pa.dec.com!rust.zso.dec.com!shlump.nac.dec.com!engage!ootool.dec.com!tenny
From: tenny@ootool.dec.com (Dave Tenny)
Newsgroups: comp.sys.next
Subject: Re: How do make Objective-C handle circular class references, HELP!
Message-ID: <1991Feb19.130034.4934@engage.enet.dec.com>
Date: 19 Feb 91 12:55:05 GMT
Sender: news@engage.enet.dec.com (USENET News System)
Organization: Digital Equipment Corporation
Lines: 19


Following up on my base topic for the question on circular Objc classes,
please note that I used the term "Static binding" loosely for
the Objc method applies when the object receiving the message has a
more specific type than "id".  There is no static binding in Objc
that I know of, though it's supposed (not sure where I read this)
to be a faster method lookup if you to declare explicit classes for
objects.  And if you want to remove the general dynamic method lookups,
you can obtain the method address yourself when you start up, and funcall
it in place of method apply for future calls.  But it's rarely going to
be worth the trouble.

I'm still hoping for a solution to the circular reference problem.
I've had two replies (thanks to those who replied) with what amount to
Objc condolances :-). 

Now, does anybody have a real fix?  Please?

Dave