Re: Danger: @true and @false aren't considered booleans
Re: Danger: @true and @false aren't considered booleans
- Subject: Re: Danger: @true and @false aren't considered booleans
- From: Sean McBride <email@hidden>
- Date: Thu, 23 Aug 2012 13:46:24 -0400
- Organization: Rogue Research Inc.
On Sat, 18 Aug 2012 22:13:07 -0700, Jens Alfke said:
>> @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.)
Give the issues discussed in this thread, I don't see any reason to use @true instead of @YES. Do you just have some personal preference for the true/false nomenclature over YES/NO?
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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