Following the release of iOS 6.1, Apple has updated its Xcode developer toolset as well. The new version, Xcode 4.6, includes improvements in code completion heuristics, new compiler warnings, and other coding improvements.

Quote:

What's new

- Includes SDKs for OS X 10.8 Mountain Lion and iOS 6.1.
- Code completion heuristics are more accurate, and use an optimized default data set.
- New compiler warnings help identify potential bugs when using ARC and weak references.
- C++11 support for 'user defined literals' and 'unrestricted unions' features.
- Debugger can inspect elements within NSArray or NSDictionary objects.
- Analyze now performs deeper cross-function static analysis of Objective-C and C++ code.
- The number of indexing passes is reduced due to improved dependency checking.
- Additional bug fixes and stability improvements.

This should have been in XCode 3! Been needing this for years and has added hours to my life adding logging statements to see the contents of these.

I'm hoping this is the start of a much-needed and long overdue ramp up of the debugger support. For me, at least, it's the weakest part of the XCode experience by far.

I'm giving them a pass for getting things on track with lldb and see this latest change as a step in the right direction. I'm hoping they'll run with it from here the way they have with the static analysis etc.

I didn't touched XCode recently too much. Anyone has a hint for me if the wireless deployment meanwhile is back ? I found the idea of XCode 4.2 to wireless manage devices nice; less dealing with cables. It got removed in 4.3 but never showed up again. Was there any statement from Apple ? Just curious ...

Bracket completion hasn't been fixed. Also the dictionary inspector doesn't support CFDictionaryRef or CFMutableDictionaryRef objects :sigh:

You can work around it by telling it to display as an NSDictionary, but that's not really a solution.

Apple generally prefers you work with Objective-C style objects. Core Foundation is just there to enhance C compatibility... They haven't even given Core Foundation ARC yet. It's a bit of a second-class citizen in general.

*Had* to update to 4.6 after updating my iP5 to 6.1 (of course, right in the middle of something), then XC terminated trying to startup after the install, finally got it sorted out, got my 6.1 deployment target up and running again. Fixed some munged up tablecells too (just the visual layout in storyboard).

__________________‎"Of my friend, I can only say this: of all the souls I have encountered in my travels, his was the most... human." ~Captain James T. Kirk

Press Cmd+F to open a find dialog, type some query that gets lots of results, press Enter to select next result, it works fine, but Shift+Enter has a problem - it goes to previous entry, then to next one, effectively looping in place.

Apple generally prefers you work with Objective-C style objects. Core Foundation is just there to enhance C compatibility... They haven't even given Core Foundation ARC yet. It's a bit of a second-class citizen in general.

Yeah but C compatibility is kind of important. Also, unless you're targeting iOS6 (and NSMapTable, which I'm unsure if this new inspector will detail), it's the only way to get a dictionary that doesn't copy its keys or retain its values.

As for bracket autocompletion, the problem is this:

4 + 3

4 + 3 )

(4 + 3 ) now press space...

( )4 + 3 ) why does XCode insert this bracket?!

I like the bracket autocompletion in general, but this one thing just annoys the hell out of me. There's nothing to complete here, the brackets are already closed.

Yeah but C compatibility is kind of important. Also, unless you're targeting iOS6 (and NSMapTable, which I'm unsure if this new inspector will detail), it's the only way to get a dictionary that doesn't copy its keys or retain its values.

As for bracket autocompletion, the problem is this:

4 + 3

4 + 3 )

(4 + 3 ) now press space...

( )4 + 3 ) why does XCode insert this bracket?!

I like the bracket autocompletion in general, but this one thing just annoys the hell out of me. There's nothing to complete here, the brackets are already closed.

Yeah but C compatibility is kind of important. Also, unless you're targeting iOS6 (and NSMapTable, which I'm unsure if this new inspector will detail), it's the only way to get a dictionary that doesn't copy its keys or retain its values.

As for bracket autocompletion, the problem is this:

4 + 3

4 + 3 )

(4 + 3 ) now press space...

( )4 + 3 ) why does XCode insert this bracket?!

I like the bracket autocompletion in general, but this one thing just annoys the hell out of me. There's nothing to complete here, the brackets are already closed.

I've noticed this quite often too. Sometimes the I realize I need to enclose something in brackets after it's been typed, so I put the end bracket first since i'm already at the end, then go to the beginning, and magically that extraneous bracket appears. Ah well, it's clearly a very simple logic error that would take all of five seconds to fix, they just have to do it...