🚀 go-pugleaf

alex@cs.umd.edu (Alex Blakemore) writes:

>In article <timm.717827168@xongmao> timm@xongmao.ncsa.uiuc.edu (Tim McClarren) writes:
>> Well, I can't seem to find a rationale for the changes, although I 
>> did find them documented in ObjC.rtf in the Developer Release Notes.
>> I am having the same problem as the original poster.  And the Release Notes
>> don't make the behavior any clearer to me.  I should think that these
>> things should both return YES or both return NO.  Any other clues?

>the difference between the IsKindOf and IsMemberOf methods (and their cousins
>that take class names instead of class objects as args) is how they handle subclasses.
>if an object x is an instance of class B (which is a subclass of A) then
>x is a kind of A but x is NOT a member of A.
>(x is both a kind of B and a member of B)

>for more info look in the concepts section on objective C or the
>reference for the class Object.

That's not what was being discussed, nor is it what you said in
your former post.  I was already well aware of the differences between
the "isKindOf:" and "isMemberOf:" methods.
So the questions still stands: where is the rationale documented,
and why is gdb exhibiting this odd behavior?

Anyone, anyone?

-- 
Tim McClarren     | "...a bajillion brilliant Jobsian lithium licks."
timm@ncsa.uiuc.edu|
(217)244-0015     |