• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Static analyser less rigorous nowadays?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Static analyser less rigorous nowadays?


  • Subject: Re: Static analyser less rigorous nowadays?
  • From: steven hooley <email@hidden>
  • Date: Fri, 16 Dec 2011 10:12:29 +0000
  • Importance: Normal

eek! Just to clarify, that isn't real code. The actual case was more subtle, but on investigation I was surprised that nothing i could do could provoke the Static Analyser when a method argument was involved.
I can sort of understand why this has to be.. but would be interested if anyone has any thoughts.
Martin Wierschin wrote:
> It does seem like the static analyzer should have given you warnings for
> that mess. It certainly would be best if it did!


> On 2011.12.09, at 3:57 AM, steven hooley wrote:

>> - (void)foo:(NSString *)bar {
>> [bar release];
>> [bar release];
>> [bar release];
>> [bar release];
>> id boo = bar;
>> [boo release];
>> [boo release];
>> [boo release];
>> [boo release]; 
>> }
 _______________________________________________
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

  • Prev by Date: Re: Turn off automatic snapshots
  • Next by Date: Unknown CF Error
  • Previous by thread: Re: Static analyser less rigorous nowadays?
  • Next by thread: Generating CoreData accessors Xc4?
  • Index(es):
    • Date
    • Thread