meterman opened this issue on Feb 29, 2008 · 94 posts
kuroyume0161 posted Sun, 02 March 2008 at 1:34 PM
The Mac isn't completely 64-bit (eh hem). With Leopard 10.5 (!), the kernel and frameworks have been made 64-bit. I'm not certain that anything in that screenshot regards it either. Multiple CPUs isn't a 64-bit thing - I've been running dual processors since 2000 under Windows 32-bit (and Linux has supported them for a lot longer). ;P
Some edumication:
http://www.theregister.co.uk/2003/07/07/mac_os_x/
http://en.wikipedia.org/wiki/Mac_OS_X_v10.4 (scroll down to "Improvements")
http://developer.apple.com/macosx/64bit.html
There is no 64-bit Carbon support until Leopard - one MUST use Cocoa otherwise. And the Carbon GUI is completely 32-bit until Leopard. Even with Leopard, there are still gaps. This is the main, overriding reason why Maxon has not made a 64-bit version of Cinema 4D for MacOS:
http://www.carbondev.com/site/?page=64-bit+Carbon
Unfortunately, 0.0001% of the developers in the entire universe use (or even know about) Apple's proprietary Objective-C language. There are stubs and wrappers to use C/C++ with it, but, imho and that of a large number of developers, it ain't worth the aggravation. J++ and C# and Objective-C - say no to OS-dependent programming languages for multi-platform dev.
And finally, can anyone provide a list or link thereof with MacOS X 64-bit software? I see that Adobe Photoshop translated early. Can't find much else four years later.
http://www.geekpatrol.ca/2006/09/32-bit-vs-64-bit-performance/
*But seriously - is it possible to have a 64 bit cpu on a 32 bit board? SO what exactly is it that makes a mobo 32 or 64 bit anyway?
No. The mobo needs to support the 64-bit addressing and register spaces of the cpu and memory.
See ya...
C makes it easy to shoot yourself in the
foot. C++ makes it harder, but when you do, you blow your whole leg
off.
-- Bjarne
Stroustrup
Contact Me | Kuroyume's DevelopmentZone