Class hierarchy weirdness.
Class hierarchy weirdness.
- Subject: Class hierarchy weirdness.
- From: Kigney <email@hidden>
- Date: Thu, 18 Apr 2002 02:27:05 -0700 (PDT)
In my program, I have a class hierarchy looks like
this, from top to bottom:
NSObject
MyObject
Character
When [characterInstance dealloc] is called, though,
something _very_ strange happens. Here's my best
attempt to diagram it as a stack. Note: all of the
methods below call [super dealloc] at the end of their
own dealloc methods.
[characterInstance dealloc]
[myObjectInstance dealloc]
[characterInstance dealloc]
[myObjectInstance dealloc]
Signal 11, or signal 10. The program
quits.(Probably because it's trying to re-deallocate
myObjectInstance's data members.)
If my program's class hierarchy is well defined (and
I've checked the header files about twenty times now),
is there any reason why an object's super would
consider its child its super? If not, why might a
problem like this occur? Where should I look?
God, I feel stupid, but I retyped this e-mail about 4
times trying to make it make more sense. Hope you
could understand it. Thanks for any help in advance.
-Josh
email@hidden
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.