- The compiler automatically calls
@synthesizeby default for unimplemented
- For the
NSDictionaryclasses, support is provided for Objective-C literals.
- Subscripting using
'[ ]'syntax is supported for Objective-C container objects.
- Compatibility with the C++11 standard is improved.
- New static analyzer checks for common security mistakes in API and malloc usages.
- The caller and callee for selected methods can be displayed in the Assistant Editor.
- Code completion is enhanced with QuickHelp.
- Scene Kit is supported with a viewer-editor for 3D document files.
- Improved localization workflow uses base language
- Git supports staging of individual changes.
Leave it to Apple to introduce core language features in a point release of their IDE!
Anyway, it got me thinking about Objective-C, productivity, and John Siracusa’s comments from a few years back:
A framework with methods like this:
NSInteger myCount = [[myDict objectForKey:@"count"] integerValue]; NSArray *myArray = [myString componentsSeparatedByString:@","]; myItem = [myArray objectAtIndex:i];
is just not going to fly in a language that (hypothetically) supports this:
myCount = myDict["count"]; myArray = myString.split(","); myItem = myArray[i];
Looks like John finally got his wish! And quite frankly, it’s about time. It doesn’t get much more basic than strings and arrays, and it boggles my mind that it took Apple this long to give us a non-eye-gouging syntax. Don’t get me wrong; I’m glad to have these improvements. It’s just that in my opinion, ObjC still lags far, far behind the rest of the civilized world when it comes to programmer productivity.
Over the next little while I will be taking a closer look at some of Objective-C’s productivity failures in comparison with languages like C#, Ruby, Python, and F#.