Ah, yeah, that makes sense. But looking at the overall code now I'm not sure that it does. So, here's what actually happens at the [MKAsyncRequest facebookUsersGetInfo...] call:
+(void)facebookUsersGetInfo:(NSArray *)uids fields:(NSArray *)fields facebookConnection:(MKFacebook *)aFacebookConnection delegate:(id)aDelegate selector:(SEL)aSelector {
self = [[MKAsyncRequest alloc] initWithFacebookConnection:aFacebookConnection delegate:aDelegate selector:aSelector];
[NSURLConnection connectionWithRequest:[NSURLRequest requestWithURL:[aFacebookConnection facebookUsersGetInfoURL:uids fields:fields]] delegate:self];
}
seeing as the NSURLConnection method is asynchronous, releasing before it's done would be bad too.
Thoughts?
Paul
----------Original Message----------
On 4/28/07 13:32 , Scott Stevenson (email@hidden) wrote:
>
> On Apr 28, 2007, at 11:49 AM, Paul Borokhov wrote:
>
>> The reason I was thinking that the [self release] is legal is
>> because the object is initially created with an instance method that
>> calls [super init] (not a convenience class method), and so it seems
>> to make sense that someone needs to release it too.
>
> Ah, I see. Actually, In a situation like this:
>
> - (id)init
> {
> if (self = [super init])
> {
> //...
> }
> return self;
> }
>
> You're not responsible for releasing yourself later, the original caller is.
>
> If helps to arrange things in your head, keep in mind [self release]
> is not the counterpart to [super init].
>
> That is, "self" refers to an instance, "super" refers to a class.
>
> - Scott
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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/email@hidden
This email sent to email@hidden
