I generally recommend that you move off NSLog
and on to the actual system log APIs. See Your Friend the System Log.
However, that won’t fix this problem. Historically NSLog
would internally render your arguments to a string and then log that string. This was less than ideal because it disables all the optimisations available to the system log. Now that Xcode has system log integration, NSLog
can log to that directly, and regain those optimisations. However, in the system log model the client (meaning Xcode in this case) is responsible for rendering the values that were recorded, and that presents some challenges.
I’m not sure if Xcode has enough info to get you back to where you want to be, but it’s definitely worth filing a bug requesting that.
Please post your bug number, just for the record.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"