On Thu, Jul 24, 2008 at 1:35 PM, Nate Weaver <[EMAIL PROTECTED]> wrote:
> You're right, of course (I forgot about this).
>
> I think I decided not to worry about it too much since it shouldn't make it
> into production code (if it does, then I did something wrong). My main goal
> was to keep the ma
You're right, of course (I forgot about this).
I think I decided not to worry about it too much since it shouldn't
make it into production code (if it does, then I did something wrong).
My main goal was to keep the macro as simple as I could (or at least,
not have to break it onto multiple
By carefull with the basename function. Theoricaly, it require a
mutable string (char * and not const char *), so this logging function
may crash (even it for now it works).
Le 23 juil. 08 à 20:01, Nate Weaver a écrit :
This is the route I follow. I use normal NSLog() statements for
condit
Andrew Merenbach wrote:
Is there anything particularly wrong with NSLog statements being in
a release package? Performance wise? Security wise? Just wondering
the root of the question.
I'd say that the most important reason for removing the NSLog()
statements *might* be the look of the program
> On Jul 23, 2008, at 6:48 PM, Mike 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 com
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
T
at 8:18 AM, Ian was here wrote:
Try this
#ifdef DEBUG
NSLog("Whatever");
#endif
--- On Wed, 7/23/08, Mike <[EMAIL PROTECTED]> wrote:
From: Mike <[EMAIL PROTECTED]>
Subject: NSLog on releasebuild
To: "Cocoa-Dev List"
Date: Wednesday, July 23, 2008, 7:48 A
def DEBUG
NSLog("Whatever");
#endif
--- On Wed, 7/23/08, Mike <[EMAIL PROTECTED]> wrote:
From: Mike <[EMAIL PROTECTED]>
Subject: NSLog on releasebuild
To: "Cocoa-Dev List"
Date: Wednesday, July 23, 2008, 7:48 AM
Hello,
During development and debug I typically
On Jul 23, 2008, at 6:48 PM, Mike 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 o
On Wed, Jul 23, 2008 at 8:33 AM, Phillip Jacobs <[EMAIL PROTECTED]> wrote:
> Is there anything particularly wrong with NSLog statements being in a
> release package? Performance wise? Security wise? Just wondering the root of
> the question.
1) Possible performance issue (just burning CPU for some
On Wed, Jul 23, 2008 at 7:48 AM, Mike <[EMAIL PROTECTED]> 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?
>
> S
w
On Jul 23, 2008, at 8:18 AM, Ian was here wrote:
Try this
#ifdef DEBUG
NSLog("Whatever");
#endif
--- On Wed, 7/23/08, Mike <[EMAIL PROTECTED]> wrote:
From: Mike <[EMAIL PROTECTED]>
Subject: NSLog on releasebuild
To: "Cocoa-Dev List"
Date: Wednesday,
opening quote:
NSLog(@"Whatever");
Cheers,
Andrew
On Jul 23, 2008, at 8:18 AM, Ian was here wrote:
Try this
#ifdef DEBUG
NSLog("Whatever");
#endif
--- On Wed, 7/23/08, Mike <[EMAIL PROTECTED]> wrote:
From: Mike <[EMAIL PROTECTED]>
Subject: NSLo
rote:
From: Mike <[EMAIL PROTECTED]>
Subject: NSLog on releasebuild
To: "Cocoa-Dev List"
Date: Wednesday, July 23, 2008, 7:48 AM
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 mes
Try this
#ifdef DEBUG
NSLog("Whatever");
#endif
--- On Wed, 7/23/08, Mike <[EMAIL PROTECTED]> wrote:
> From: Mike <[EMAIL PROTECTED]>
> Subject: NSLog on releasebuild
> To: "Cocoa-Dev List"
> Date: Wednesday, July 23, 2008, 7:48 AM
> Hello
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
the
16 matches
Mail list logo
