Thanks for the feedback everyone.
I was confusing how I was going about doing the necessary initialization to be
able implement the protocol in a class. I've been using the +initialize method
to do this, but this is as someone pointed out is an implementation detail. So
adding +initialize to th
Begin forwarded message:
> From: Maxthon Chan
> Subject: Re: Protocols and the +initialize class method
> Date: August 23, 2013 at 23:30:19 GMT+8
> To: Fritz Anderson
>
> Well you can category on NSObject to perform the checking.
>
> Sent from my iPhone
>
>&g
On Aug 23, 2013, at 10:30 AM, David Duncan wrote:
> On Aug 23, 2013, at 2:49 AM, Kevin Meaney wrote:
>
>> I have a protocol where I would like to include the class method
>> +(void)initialize as being required. This way all classes that conform to
>> the protocol have to implement initializ
On Aug 23, 2013, at 10:30 AM, David Duncan wrote:
> On Aug 23, 2013, at 2:49 AM, Kevin Meaney wrote:
>
>> I have a protocol where I would like to include the class method
>> +(void)initialize as being required. This way all classes that conform to
>> the protocol have to implement initializ
On Aug 23, 2013, at 2:49 AM, Kevin Meaney wrote:
> I have a protocol where I would like to include the class method
> +(void)initialize as being required. This way all classes that conform to the
> protocol have to implement initialize as part of the protocol. I suppose I'm
> wondering if any
On 23 Aug 2013, at 4:49 AM, Kevin Meaney wrote:
> I have a protocol where I would like to include the class method
> +(void)initialize as being required. This way all classes that conform to the
> protocol have to implement initialize as part of the protocol. I suppose I'm
> wondering if anyo
Hi all,
I have a protocol where I would like to include the class method
+(void)initialize as being required. This way all classes that conform to the
protocol have to implement initialize as part of the protocol. I suppose I'm
wondering if anyone perceives any problem with doing this?
For ex
