Re: Singleton as a common area?
Re: Singleton as a common area?
- Subject: Re: Singleton as a common area?
- From: James Hober <email@hidden>
- Date: Wed, 20 Feb 2008 13:03:28 -0800
On Feb 20, 2008, at 12:04 PM, Jerry LeVan wrote:
It seems to me that a singleton object could be used
to hold lots of global state info and it would be
easy to instantiate the singleton in each of the
source files to access the stashed info...
Is this a reasonable way to share info?
Sometimes you just create a single instance of a class.
Other times you enforce that only zero instances or one instance can
ever be created. To do this second thing,
http://developer.apple.com/documentation/Cocoa/Conceptual/
CocoaFundamentals/CocoaObjects/chapter_3_section_10.html
Then you can use your singleton,
#import "Foo.h"
[Foo sharedFoo];
which is nice because now you don't have to keep track of instances
of Foo. You just get THE instance right from the class method.
The documentation above explains when this is a good way to do things.
James
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden