The canonical implementation of a singleton class uses a static to
hold the singleton instance. There are other examples in Apple sample
code of using class statics. So, I would say that it's not frowned
upon as long as there's a good reason to do it.
Luke
On Oct 6, 2009, at 4:48 PM, Colin Howarth wrote:
Hi,
I'm coming across the odd instance where the use of a class variable
would seem to make sense.
I can do this with a static definition in the class implementation
file, I suppose.
Question is: is this particularly frowned upon in the Cocoa world?
If so, why?
Thanks,
--colin
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/luketheh%40apple.com
This email sent to [email protected]
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
