Re: newie question
Re: newie question
- Subject: Re: newie question
- From: email@hidden
- Date: Mon, 08 Dec 2008 09:32:41 -0500
That's probably what I read and confusticated it with NSLog.
Thanks for setting me straight...
Back to my project...:)
Quoting Bryan Henry <email@hidden>:
The macro, by the way, would be something like this:
// Debug-build logging macro
#ifdef DEBUG
#define debugLog(format, ...) NSLog(format, __VA_ARGS__)
#else
#define debugLog(format, ...) // Nothing
#endif
Then you just add "DEBUG" as a preprocessor definition for your Debug
configuration (GCC_PREPROCESSOR_DEFINITIONS is the setting name), and
use debugLog() instead of NSLog(). You can of course customize that to
your project's needs.
Otherwise, your log messages are going to get logged to your users'
Consoles, which could be very annoying for them.
Bryan
P.S. Jon - You're probably thinking of NSAssert(), which you can strip
out by defining NS_BLOCK_ASSERTIONS.
On Dec 8, 2008, at 8:53 AM, Jean-Daniel Dupas wrote:
NSLog is not stripped out of released build.
You have to use your own macro to achieve this.
Le 8 déc. 08 à 14:24, Jon C. Munson II a écrit :
Depending upon the language you are developing in, you can also
use NSLog which will output to the console window AND I believe
it will get stripped from your final app upon compile.
Where does printf command output go?. I mean, is there something
like an output console on xcode?.
I'd found very usefull to see some results as you are developing
your program.
thanks
--
Oscar A. Alvarado
_______________________________________________
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
_______________________________________________
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