On Thu, Jun 25, 2009 at 2:56 AM, Jean-Daniel
> Actually it does not warn. But IMHO it should. What if 'someArray' is a
> subclass of NSArray that does not retain its content (a CFArray created
> using NULL callback for example) ?
It definitely shouldn’t warn for the above case; it’s a common pattern
that would lead to too many false positives.
> And even with a standard NSMutableArray, it does not warn if you do
> something like this but should too:
> id someObject = [[MyObject alloc] init];
> [someArray addObject:someObject];
> [someArray removeObject:someObject];
> [someObject release];
> [someObject doSomething];
In this case it would be nice for it to warn. Mind you, I doubt it’s a
common enough bug to be worth the effort of implementing it.
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