Re: Including Cocoa in a Carbon App
Re: Including Cocoa in a Carbon App
- Subject: Re: Including Cocoa in a Carbon App
- From: Nick Zitzmann <email@hidden>
- Date: Wed, 29 Dec 2010 16:01:52 -0700
On Dec 29, 2010, at 3:41 PM, Jason T. Slack-Moehrle wrote:
> In my code (which is OS X and Windows) I am currently using #ifdef __APPLE__ for Apple specific items, I need to move this to Objective-C and call from CPP should I switch to __OBJC__ instead of __APPLE__?
Yes, if that Mac-specific code is written using ObjC. __OBJC__ will not be defined for code residing in C and C++ source files.
> I am presuming from your solution that __APPLE__ just means the platform of OS9 or OS X and Objective-C is not on OS 9.
Correct. You're not still targeting Mac OS 9, are you? Mac OS 9 was deprecated almost ten years ago, and I haven't seen anyone use it in a very long time.
> I thought that __MACH__ ensured OS X? Which I take it also could not imply __OBJC__
Correct.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
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