The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
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