Re: Carbon removal
Re: Carbon removal
- Subject: Re: Carbon removal
- From: Jerry Krinock <email@hidden>
- Date: Thu, 04 Jul 2013 08:49:44 -0700
On 2013 Jul 04, at 02:14, Uli Kusterer <email@hidden> wrote:
> What this does is switch the entire application to be compiled as 64-bit,
Yes, you're correct, Uli. I moshed in the 64-bit conversion with this as extra insurance.
> which just happens to have the side-effect of not supporting most of the deprecated Carbon calls.
If you simply use the latest SDK, will you not supposedly get compiler warnings of *all* deprecated calls, Carbon or otherwise?
> Now you’ll have to port to 64-bit eventually anyway, but it might help to first go over your code and look for any longs you’re using and make sure they’re turned into int32_t or uint32_t if they’re supposed to stay 32 bit, or use intptr_t or void* for any types that are supposed to be the size of a pointer.
Yes, and there's a whole document on converting old apps to 64 bit.
https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/64bitPorting/transition/transition.html#//apple_ref/doc/uid/TP40001064-CH207-TPXREF101
_______________________________________________
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