Re: Understanding the docs. UIApplication for iOS
Re: Understanding the docs. UIApplication for iOS
- Subject: Re: Understanding the docs. UIApplication for iOS
- From: Alex Zavatone <email@hidden>
- Date: Mon, 03 Jun 2013 20:37:55 -0400
On Jun 3, 2013, at 7:42 PM, gweston wrote:
> Alex Zavatone wrote:
>
>> > I think you might have some confusion about what a protocol is in Obj-C, which might be making it hard to frame your question in terms that make sense to the rest of us.
>>
>> It's not what a protocol is that's confusing (a neatly packaged set of methods geared for a specific purpose), ...
>
> And yet, that's really not a good definition of what a protocol is. That's closer to a category.
OK, how about what I said + "for the purpose of establishing a formal mechanism for classes to talk to each other"?
> Really the best description of a protocol is the definition of the word protocol itself. It's a sort of contract that defines the way one object can assume it's able to interact with another. It's not a set of methods but of messages. So back to your first post:
>
> "It's not listed that the UIApplication class conforms to the UIApplicationDelegate, ..."
>
> Right. Because UIApplication *does not* conform to UIApplicationDelegate. It's a client of that protocol.
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden