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: Joanna Carter <email@hidden>
- Date: Mon, 18 Apr 2011 09:05:28 +0100
H Scott
>> 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…
Yes; after the first few projects, based on the default Core Data project template, I started to realise that this (separating out the Core Data stack) was an excellent case for a singleton/static class.
Can someone tell me if it is just a matter of adding/modifying class files in the templates folder to make this happen every time?
Joanna
--
Joanna Carter
Carter Consulting
_______________________________________________
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