mstecker said:Huh? Carbon code is just as easy to compile for x86 as Cocoa code. Just hit the magic button and it's done. Now Adobe does have some challenges - likely porting from CodeWarrior to XCode (2 developers for 2 weeks tops), porting all of the custom altivec code (probably not too hard because they already have the intel optimized code for the Windows builds).
This is - for some reason - a fallacy that I've heard over and over about the x86 transition. Carbon code will recompile and run on x86. New apps can be written for x86 using the Carbon APIs.
Matthew
Matthew, you either have no idea what you are talking about or you know much more than I do. Granted, I'm not much of a developer but it was Apple that told me at WWDC that Carbon libraries won't be supported in Universial Binaries. This was part of the reason why Apple is making people move away from Codewarrior, because you have to write in pure Cocoa and for some reason I didn't catch XCode was more applicable.
This is what Apple says about Codewarrior..
"Move your application from CodeWarrior to Xcode and be ready for Intel-based Macs."
I'm trying to find some information at Apple's dev site but it's pretty vague. Carbon is mentioned in the transition documents as if it were a valid set of libraries for Univeral apps so perhaps you are correct (maybe something changed since wwdc). However, at least one Apple doc says that to compile Universal binaries, you need to be in a certain group.. those that have cocoa, carbon, java.. apps that compile already and it goes to list another group with Win32 apps that compile already so that document isn't saying that Carbon is supported natively but rather that you can port from Carbon (and Win32) to make universal binaries.
Honestly, I'm not sure. I do remember, clearly, Apple saying that Carbon would not be a supported API anymore while I was at WWDC. ((I'm much more of a sys-admin than a developer so I don't have very good first hand knowledge on these matters))
ffakr.