On Aug 11, 2012, at 7:56 PM, Graham Cox <graham....@bigpond.com> wrote:
> On 12/08/2012, at 10:46 AM, Charles Srstka <cocoa...@charlessoft.com> wrote: > >> Well, that's not necessarily true — if one's codebase is heavily dependent >> on Carbon or any of the other various technologies that didn't make the >> 64-bit transition, porting to 64-bit may be quite involved. However, this >> even further underscores the need to get started sooner rather than later. > > Fair comment, though I would suggest that if you are still using a Carbon > codebase at this point and have so far done *nothing* to transition your > code, it's already far too late. The writing has been on the wall for Carbon > far longer than it has been for 32-bit Cocoa. Well I dunno, since Mountain Lion was just released last month, you've got almost a year, so I wouldn't say it's too late already. If you've got a *large* Carbon codebase, then yeah, you're not going to get it done on time, but it's better to be at least *partially* done by the time Carbon goes away. Sitting around and saying "oh, leaving my app 32-bit forever will be fine because this two-year-old document said I don't have to convert to 64-bit!", OTOH, is not a productive strategy. Charles _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
