• 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: Danger: @true and @false aren't considered booleans
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Danger: @true and @false aren't considered booleans


  • Subject: Re: Danger: @true and @false aren't considered booleans
  • From: Jens Alfke <email@hidden>
  • Date: Sat, 18 Aug 2012 22:13:07 -0700


On Aug 18, 2012, at 9:54 PM, Roland King <email@hidden> wrote:

@YES and @NO however required a header change (to use those __objc_yes and __objc_no values), and that only showed up in 10.8 headers, but as long as you have that SDK, you can target something less than 10.8 and it will be fine. Xcode 4.4 building for iOS however still doesn't have them because the 5.1 headers don't have them. 

Groan. OK, _definitely_ going back to the old-style syntax for booleans. (Which in my case is $true and $false from my MYUtilities library.)
Thanks for the heads-up.

—Jens

 _______________________________________________
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

  • Follow-Ups:
    • Re: Danger: @true and @false aren't considered booleans
      • From: Sean McBride <email@hidden>
References: 
 >Danger: @true and @false aren't considered booleans (From: Jens Alfke <email@hidden>)
 >Re: Danger: @true and @false aren't considered booleans (From: Roland King <email@hidden>)
 >Re: Danger: @true and @false aren't considered booleans (From: Jens Alfke <email@hidden>)
 >Re: Danger: @true and @false aren't considered booleans (From: Roland King <email@hidden>)
 >Re: Danger: @true and @false aren't considered booleans (From: Roland King <email@hidden>)

  • Prev by Date: Re: Danger: @true and @false aren't considered booleans
  • Next by Date: Re: Danger: @true and @false aren't considered booleans
  • Previous by thread: Re: Danger: @true and @false aren't considered booleans
  • Next by thread: Re: Danger: @true and @false aren't considered booleans
  • Index(es):
    • Date
    • Thread