Re: NSLog on releasebuild
Re: NSLog on releasebuild
- Subject: Re: NSLog on releasebuild
- From: Nate Weaver <email@hidden>
- Date: Wed, 23 Jul 2008 13:01:09 -0500
This is the route I follow. I use normal NSLog() statements for
conditions that "should never happen", and DebugLog() for debugging:
#ifdef DEBUG
#define DebugLog(s, ...) NSLog((@"%s %s:%d " s), __func__,
basename(__FILE__), __LINE__, ## __VA_ARGS__);
#else
#define DebugLog(s, ...)
#endif
The extra info is for context.
On Jul 23, 2008, at 11:22 AM, Shawn Erickson wrote:
On Wed, Jul 23, 2008 at 7:48 AM, Mike <email@hidden> wrote:
Hello,
During development and debug I typically use tons of NSLog()-
messages to get
info what's happening.
I don't wish to include these messages to release-build so what is
common/recommended way to get rid of them?
Should I comment them all out or is there some easier way to
disable them or
should I just leave them as they are?
In theory you could do something like the following (not tried this
myself)...
#if defined(DEBUG) // or some other trigger for debug logging
#define DLog(...) NSLog( __VA_ARGS__ )
#else
#define DLog(...)
#endif
... then in code ...
DLog(@"blah");
DLog(@"blah %@", someObject);
etc.
-Shawn
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden