On Tue, 9 Mar 2010 23:58:55 +, Jeff Laing
said:
>The upshot was that apparently the iPhone developers like you to avoid the use
of autorelease pools where possible. One hidden difference in the above is that
in the first case you have (probably) populated the autorelease pool and in the
other
> For example, is:
>
> NSMutableArray *anArray = [[NSMutableArray array] retain];
>
> better than:
>
> NSMutableArray *anArray = [[NSMutableArray alloc] init];
I've been reamed, in the recent past, for expressing the opinion that the first
was just as good as the second - apparently the answer
On Tue, 9 Mar 2010 13:41:03 -0800, Laurent Daudelin said:
>I've been running in that situation and I'm just wondering if there are
>any advice for/against one or the other method.
>
>For example, is:
>
>NSMutableArray *anArray = [[NSMutableArray array] retain];
>
>better than:
>
>NSMutableArray *a
On Mar 9, 2010, at 2:50 PM, Alexander Spohr wrote:
> I’d use
> NSMutableArray *anArray = [NSMutableArray new];
> in this case ;)
FWIW, I prefer to use alloc-init for one main reason: When I want to look for
places in the code that initialize certain objects (which does happen in large
code bas
Am 09.03.2010 um 22:44 schrieb Luke the Hiesterman:
>
> On Mar 9, 2010, at 1:41 PM, Laurent Daudelin wrote:
>
>> I've been running in that situation and I'm just wondering if there are any
>> advice for/against one or the other method.
>>
>> For example, is:
>>
>> NSMutableArray *anArray = [
On Mar 9, 2010, at 1:41 PM, Laurent Daudelin wrote:
> I've been running in that situation and I'm just wondering if there are any
> advice for/against one or the other method.
>
> For example, is:
>
> NSMutableArray *anArray = [[NSMutableArray array] retain];
There is no reason to use this wh
