Re: No longer use NSLog() in Xcode 4?
Re: No longer use NSLog() in Xcode 4?
- Subject: Re: No longer use NSLog() in Xcode 4?
- From: Jerry Krinock <email@hidden>
- Date: Sat, 17 Sep 2011 15:23:16 -0700
Quite a few cool ideas suggested in this thread; thanks.
To shotgun in NSLogs, I've added several Code Snippets. Some of them use strrchr() as George Warner does to shorten __FILE__ or __PRETTY_FUNCTION__. <#Token#> is handy.
To remove shotgunned NSLogs en masse, I want a Behavior with a keyboard shortcut to an external script. Some trouble accessing the source files in a project, but that's another topic.
* * *
To Douglas Davidson: Regarding Xcode 4.1 taking tens of seconds to load breakpoints, the actual problem was that Xcode was carrying too much baggage in memory. This was probably due to several prior Internal Errors, when it asked me if I wanted to "Crash" or "Continue", and I chose "Continue". Relaunching Xcode solved the problem. So, at least in a small project, I'm leaving the "Breakpoints" button pushed in now.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden