When we assign memory to a class variable, should we release it or set it to nil in dealloc method? What is the best practice?
Source: Tips4all, CCNA FINAL EXAM
Source: Tips4all, CCNA FINAL EXAM
I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?
Best practice:
ReplyDelete[foo release]; // ensures that memory is released
foo = nil; // ensures that there is no dangling pointer to released memory
Other notes:
When you assign to a property declared to retain,
// in your .h
@property (retain) MyObject *foo;
// in your .m
self.foo = bar; // bar is retained; whatever foo previously pointed at is released
it will release what it was previously pointing at and retain the new object being assigned.
So, you can use:
self.foo = nil;
and it will release whatever foo was pointing at. However, if your property was not declared to have retain storage semantics, this will not implicitly release whatever foo was pointing at. Also, as Ryan pointed out, a property can be overridden to have side effects. For this reason, it is best to follow the pattern of always using:
[foo release];
To ensure that you don't have a dangling pointer to released memory, you can follow this up with:
foo = nil;
If you are not using properties with retain semantics, you need to release whatever was stored in the variable:
[foo release];
EDIT: Also see the following answer to another question that explains this:
iPhone - dealloc - Release vs. nil