Re: Static analyser less rigorous nowadays?
Re: Static analyser less rigorous nowadays?
- Subject: Re: Static analyser less rigorous nowadays?
- From: Martin Wierschin <email@hidden>
- Date: Tue, 13 Dec 2011 12:07:09 -0800
> The reason you don't get a warning is because you're passing result into the block and the analyser doesn't look at the block to see what's happening to it within the block. I imagine it would be quite difficult for it to support that. It could do what it does with C functions and method calls and assume that it's retain/release neutral but I suspect that would throw up too many false positives (and is probably why they haven’t already done so).
Thanks for the reply and explanation Chris. That makes sense in general, though in this case clang has the full source to the block in the same lexical scope, so it should be able to see that no retain/release methods are called. But I can understand that special casing this is an enhancement; I'll file it.
Best,
~Martin
_______________________________________________
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