Re: 64-bit vs 32-but Objective-C Runtime differenes [WAS]Re: Xcode Debugger: Cannot Step Into a Method in a x86_64 architecture build
Re: 64-bit vs 32-but Objective-C Runtime differenes [WAS]Re: Xcode Debugger: Cannot Step Into a Method in a x86_64 architecture build
- Subject: Re: 64-bit vs 32-but Objective-C Runtime differenes [WAS]Re: Xcode Debugger: Cannot Step Into a Method in a x86_64 architecture build
- From: Clark Cox <email@hidden>
- Date: Thu, 15 Jan 2009 22:51:30 -0800
On Thu, Jan 15, 2009 at 10:03 AM, Shawn Erickson <email@hidden> wrote:
> On Wed, Jan 14, 2009 at 2:36 AM, Andreas Grosam <email@hidden> wrote:
>
>> I'm a bit confused about whether we should use these 64-bit only features in
>> Xcode/Cocoa/iPhone programming, as it has been mentioned as great
>> improvements to the language several times from Apple evangelists -- or if
>> we should remove any C++ traces and use pure Objective-C. The easiest way to
>> solve the problem for Objective-C++ developers is that there are no language
>> dependencies for different architectures (by adding them into 32-bit as
>> well).
>
> (note no 64-bit runtime exists for the iPhone and likely wont exist
> anytime soon)
For all intents and purposes, the iPhone's runtime *is* the 64-bit
runtime despite being 32-bit (i.e. unified C++/Obj-C exceptions,
non-fragile instance variables, etc). Because Apple did not have any
backwards compatibility concerns with the iPhone (as they did on the
32-bit Macs) they were free to use the new runtime.
--
Clark S. Cox III
email@hidden
_______________________________________________
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