Re: initWithCoder / unarchiveObjectWithData Memory Management Question

2010-02-20 Thread Matt Neuburg
On Sat, 20 Feb 2010 01:47:27 -0500, Thomas Wetmore said: >The question came up because I found a case in my code where I convinced myself I was over-releasing an object created in this fashion You will never over-release an instance if you follow the basic rule - if and only if you yourself copie

Re: initWithCoder / unarchiveObjectWithData Memory Management Question

2010-02-20 Thread Uli Kusterer
On 20.02.2010, at 07:47, Thomas Wetmore wrote: > (error handling removed), has myObject been retained, or must I now retain > it. The unarchiveObjectWithData class method causes myObject's class's > initWithCoder object method to run. I assume that initWithCoder obeys memory > management rules a

Re: initWithCoder / unarchiveObjectWithData Memory Management Question

2010-02-20 Thread Quincey Morris
On Feb 19, 2010, at 22:47, Thomas Wetmore wrote: > from the NSKeyedUnarchiver (or any unarchiver) class. > > After the following lines of code run ... > > NSData* data = [NSData dataWithContentsOfFile: myObjectPath]; > myObject = [NSKeyedUnarchiver unarchiveObjectWithData: data]; > > (error han

initWithCoder / unarchiveObjectWithData Memory Management Question

2010-02-19 Thread Thomas Wetmore
I have a memory management question involving the interaction of: - (id) initWithCoder: (NSCoder*) coder from any class that implements and + (id) unarchiveObjectWithData: (NSData*) data from the NSKeyedUnarchiver (or any unarchiver) class. After the following lines of code run ... NSData* d