objective c - Can LLVM 4.0 Be Used in Xcode 4.3? -


In other words, use literal for iOS 5 but the goal.

I know but this post is not conclusive.

You can switch compiler out, but it does not work as much as you can think (I Now try) To use this new syntax, there are some requirements for compiling SDK (i.e. it will work on the previous iOS version, but you have to compile it with iOS 6.0 SDK). I do not think I am allowed to discuss this time, but they are widely included in the "Modern objective-C" WWDC 2012 video.

Actually, you have syntax, but libraries do not know how to answer it.

An alternative theory is, though ... that I have not done right ^^;

Finally, however, you are not not posted on the 5.x apps to 4.3. So my suggestion is just upgrading, it really does not have any negativity (unless you deploy the app soon, but in that situation there will be trouble in changing everything, because I think you have almost completed Are).

Edit (After 2 months IOS 6 is public). You can definitely use categories to fulfill the SDK requirements of new purpose-literal syntax. Add categories to NSArray and NSDictionary - (ID) objectAtIndexed subscription: (NSUInteger) idx and - (id) objectForKeyed membership: (ID) key respectively just back objectAtIndex: and objectForKey: (That's why they do anyway in iOS 6). In addition to NSMutableArray and NSMutableDictionary - (zero) setObject: (id) obj atIndexed subscription: (NSUInteger) index and - (Zero) setObject: (id) obj atIndexed subscription: (nsuentenger) index respectively if the object is not already present, and it changes if it changes.

A hold: To define boolean liters for the definition of Yes and NO to NSNumber in IOS 6 has been changed. You need to do the following:

  #if __has_feature (objc_bool) #undef Yes / Before that (BOOL) 1 #undef NO // Before (BOOL) 0 #define Yes __objc_yes #define NO __objc_no #endif   

The reason for this is that the new syntax already has a definition for @ (...) syntax) and The old definition will solve @ (BOOL) 1 which is an error.

Comments