Should I somehow release shared object (on which singleton is based) when my application terminates if no garbage collector used (iPhone environment)?
相关问题
- CALayer - backgroundColor flipped?
- What uses more memory in c++? An 2 ints or 2 funct
- Core Data lightweight migration crashes after App
- Core Data lightweight migration crashes after App
- How can I implement password recovery in an iPhone
相关文章
- 现在使用swift开发ios应用好还是swift?
- Could I create “Call” button in HTML 5 IPhone appl
- TCC __TCCAccessRequest_block_invoke
- xcode 4 garbage collection removed?
- Unable to process app at this time due to a genera
- How can I add media attachments to my push notific
- How do you detect key up / key down events from a
- “Storyboard.storyboard” could not be opened
When an application exits, all its memory is released. So it really does not matter if you release objects at all, so long as you don't use too much memory while running.
Even when the strategy changes in 4.0, a single small object won't have much impact; it will still be released along with the rest of the application when it terminates.
As an aside, you might find this useful:
http://cocoawithlove.com/2008/11/singletons-appdelegates-and-top-level.html