Re: predefined macro iOS vs OS X
Re: predefined macro iOS vs OS X
- Subject: Re: predefined macro iOS vs OS X
- From: Jean-Daniel Dupas <email@hidden>
- Date: Sat, 17 Aug 2013 19:01:14 +0200
Le 17 août 2013 à 17:55, Marcel Weiher <email@hidden> a écrit :
>
> On Aug 16, 2013, at 19:04 , Kyle Sluder <email@hidden> wrote:
>
>> On Aug 16, 2013, at 12:41 PM, "Gerriet M. Denkmann" <email@hidden> wrote:
>>> On 16 Aug 2013, at 22:59, Kyle Sluder <email@hidden> wrote:
>>>> Xcode does know this. But if you're building for 32-bit OS X, it will correctly complain.
>>>
>>> When I build for Mac OS X CGRect is accepted.
>>> But when I build for iOS then NSRect creates "Use of undeclared identifier "NSRect" did you mean "NSSet""
>>
>> Stop using NSRect in your method prototypes and just use CGRect.
>
>
> This is certainly pragmatic, effective advice.
>
> <PetPeeve>
>
> However…if you care as much about dependency management as I do (and chances are you don’t), and don’t have a direct dependency on CoreGraphics in that code (and chances are you do), then this is slightly stomach-churning, in addition to pragmatic and effective.
You don't have to add explicit dependency to anything as NSGeometry.h already does that for you.
Importing Foundation.h is enough to use CGRect on both OS X and iOS.
-- Jean-Daniel
_______________________________________________
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