Re: Namespace clash problem
Re: Namespace clash problem
- Subject: Re: Namespace clash problem
- From: Quincey Morris <email@hidden>
- Date: Thu, 13 Oct 2011 23:15:10 -0700
On Oct 13, 2011, at 18:55 , Graham Cox wrote:
> Looks like I have no choice but to change the method name for the class method at least :(
Incidentally, I've been trying to remember for months why using a class object (plus static variables) wasn't a satisfactory implementation of a singleton, and I think this was the reason. In some cases, such as what you're doing, or passing the object as an 'id' or 'void*' context parameter, you basically lose the ability to send messages to the object.
You'd probably be better off redesigning the class so that the behavior is given to a singleton instance of the class, rather than to the class itself._______________________________________________
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