On Thu, 24 Feb 2011 15:40:06 -0800, Greg Parker said: >> Unfortunately, this doesn't compile yet. This would require that LLVM >can be used for Objective-C++ modules and that the compiler flag -fobjc- >nonfragile-abi2 can be passed to the compiler driver. > >Try the Xcode 4 GM seed: the LLVM Compiler now understands C++ and >Objective-C++, and -fobjc-nonfragile-abi2 is no longer needed. > >The only remaining obstacle to ivar-in-@implementation is 32-bit Mac, >which does not support it.
Greg, The tradeoffs of using 'ivar-in-@implementation' are not clear to me. Are there some docs on this that I haven't found? What about deployment? If I build using it, can I deploy to x86_64+10.5 or only x86_64+10.6? Similarly, what are my compiler choices? No gcc, right? That means I loose the ability to measure code coverage, as clang can't do this. : ( What version of clang is needed? Is Xcode 4 the min requirement, or could I still build my code with 3.2.5? Cheers, -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
