On Mon, Nov 16, 2009 at 5:18 AM, Austin Ziegler wrote:
> Is that true anymore, though? I've been looking at a lot of sample
> code lately, and it's very common practice to use "self.foo = ..." in
> initializers, even when they're declared nonatomic. I know you said
> you don't subscribe to it, but
On Sun, Nov 15, 2009 at 10:35 AM, Clark Cox wrote:
> On Sat, Nov 14, 2009 at 11:35 PM, Ariel Feinerman
> wrote:
>> 2009/11/15 Kyle Sluder
>>> On Sat, Nov 14, 2009 at 2:35 PM, Ariel Feinerman
>>> wrote:
>>> > I need two versions of -initWith ... and -set ... methods of custom timer
>>> > class
On Sat, Nov 14, 2009 at 11:35 PM, Ariel Feinerman wrote:
> 2009/11/15 Kyle Sluder
>
>> On Sat, Nov 14, 2009 at 2:35 PM, Ariel Feinerman
>> wrote:
>> > I need two versions of -initWith ... and -set ... methods of custom timer
>> > class (for example, to prevent the circle references);
>>
>> Do no
2009/11/15 Kyle Sluder
> On Sat, Nov 14, 2009 at 2:35 PM, Ariel Feinerman
> wrote:
> > I need two versions of -initWith ... and -set ... methods of custom timer
> > class (for example, to prevent the circle references);
>
> Do not use accessors in your initializers or -dealloc.
>
Hm, it means t
On Sat, Nov 14, 2009 at 2:35 PM, Ariel Feinerman wrote:
> I need two versions of -initWith ... and -set ... methods of custom timer
> class (for example, to prevent the circle references);
Do not use accessors in your initializers or -dealloc.
--Kyle Sluder
__
Hi,
I need two versions of -initWith ... and -set ... methods of custom timer
class (for example, to prevent the circle references);
Is these correct implementation?
- (id) initWithTarget: (id) theTarget {
return [self initWithTarget: theTarget retain: YES]; // ?
}
- (id) initWithTarget: (id)
