Re: Is Apple's singleton sample code correct?
Re: Is Apple's singleton sample code correct?
- Subject: Re: Is Apple's singleton sample code correct?
- From: David Gimeno Gost <email@hidden>
- Date: Thu, 1 Dec 2005 05:14:05 +0100
On 1 Dec 2005, at 03:10, Shaun Wexler wrote:
Please refer to the "hardcore" singleton base superclass I posted a
few years ago:
<http://www.cocoabuilder.com/archive/message/cocoa/2004/2/13/97027>
If I understand it correctly, your implementation avoids the repeated
-init call problem by raising an exception if [[MySingleton alloc]
init] is called by client code. This is not the problem we were
trying to solve. We wanted to allow [[MySingleton alloc] init] to be
called as for any other class. I see no point in all that overhead
just to ensure that client code never attempts to do that.
Moreover, your implementation still has all the other problems I
mentioned about the Apple's sample code implementation, so I really
don't see what the point is here.
You're making this too difficult for yourself.
All you need to do [with my code, referenced above] to get the
behavior you want is comment out all [self doesNotRecognizeSelector:]
and [NSException raise:] messages.
Try it... sheesh! ;)
Sorry for being so dense, but I think I still don't get it:
MySingleton* herewegoagain = [MySingleton sharedInstance];
[herewegoagain release]; // <- Will -dealloc be invoked or not?
What exactly differentiates your implementation from the one suggested
by Apple's sample code, apart from solving the -init problem (at the
cost of a much, much greater complexity)?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden