Re: Proper way to create a singleton without @synchronized ?
Re: Proper way to create a singleton without @synchronized ?
- Subject: Re: Proper way to create a singleton without @synchronized ?
- From: Scott Ribe <email@hidden>
- Date: Sun, 17 Apr 2011 17:16:49 -0600
On Apr 17, 2011, at 2:46 PM, WT wrote:
> I've worked on projects where other people have made the app delegate responsible for everything and the kitchen sink. It's one thing to have a few core data stack methods in the app delegate; it's another to do a lot of one's core data tasks in the app delegate. Personally, I prefer to move all of that to a class whose sole responsibility is to manage core data tasks.
And that's good thinking. Where I tend to disagree is with the impulse to enforce every utility class to be a singleton, rather than just creating an instance and getting on with it...
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice
_______________________________________________
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