• 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: Class name as NSString and problem with NSLog?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Class name as NSString and problem with NSLog?


  • Subject: Re: Class name as NSString and problem with NSLog?
  • From: Greg Parker <email@hidden>
  • Date: Thu, 06 Mar 2014 15:47:08 -0800

On Mar 6, 2014, at 3:37 PM, Sean McBride <email@hidden> wrote:
> On Thu, 6 Mar 2014 15:15:49 -0800, Jens Alfke said:
>> I remember the “Month Of Apple Bugs”** that a hacker group ran in 2007,
>> where they published a new app or OS security vulnerability every day
>> for month. A lot of them were caused by format-string vulnerabilities.
>> Soon thereafter the compiler team at Apple added that format-string
>> security warning :)
>
> Though it still doesn't work for NSPredicate APIs:, all these years later, ex:
>
> -----------------------
> #import <Foundation/Foundation.h>
>
> int main (void)
> {
>  NSPredicate* predicate = [NSPredicate predicateWithFormat:@"foo == %d"];
>
>  return !!predicate;
> }
> -----------------------
>
> "clang -Weverything -fsyntax-only ~/test.m" gives nothing!
>
> <rdar://10699748>  Dupes welcome. :)

The problem is that +predicateWithFormat: accepts conversions that are not part of NSString's format string syntax. Adding format string warnings for new format string syntaxes requires compiler changes.


--
Greg Parker     email@hidden     Runtime Wrangler



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Class name as NSString and problem with NSLog?
      • From: Sean McBride <email@hidden>
References: 
 >Class name as NSString and problem with NSLog? (From: William Squires <email@hidden>)
 >Re: Class name as NSString and problem with NSLog? (From: Lee Ann Rucker <email@hidden>)
 >Re: Class name as NSString and problem with NSLog? (From: Jens Alfke <email@hidden>)
 >Re: Class name as NSString and problem with NSLog? (From: Sean McBride <email@hidden>)

  • Prev by Date: Re: Class name as NSString and problem with NSLog?
  • Next by Date: No longer existing outlet causes crash in new version of app (iOS)
  • Previous by thread: Re: Class name as NSString and problem with NSLog?
  • Next by thread: Re: Class name as NSString and problem with NSLog?
  • Index(es):
    • Date
    • Thread