OK, it would appear that I replied to myself on this...nice. (Tell me
again why on a discussion list like that that reply-to-list is not the
default?)
On Mar 21, 2008, at 3:27 PM, Randall Meadows wrote:
On Mar 21, 2008, at 3:11 PM, Randall Meadows wrote:
but...why aren't any of the dealloc methods being hit?
Ok, even explicitly calling -release on some objects isn't causing -
dealloc to be called.
OK, I've decided that I don't really care about this happening up
quit...I've moved the code that disconnects my session from the camera
to applicationWillTerminate:, and all is well (FSDO "all"). However...
I'm thinking I have overused "retain" on a multitude of properties I
have created. What's a good rule of thumb for using "retain" versus
"assign"? Things I explicitly allocate get "retain", whereas
objects I get from other objects get "assign"? That doesn't seem to
cover all the bases. What about objects instantiated via IBOutlet
connections? Readonly? Assign?
I'm still interested in knowing this, if anyone's got any tips or
pointers. The ObjC 2.0 doc doesn't really seem to go into much detail
about this.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
