Re: Leave NSLog()s in Final Product?
Re: Leave NSLog()s in Final Product?
- Subject: Re: Leave NSLog()s in Final Product?
- From: Allan Odgaard <email@hidden>
- Date: Fri, 12 Mar 2004 16:00:41 +0100
On 12. Mar 2004, at 15:26, Jerry Krinock wrote:
Is there any reason why I should not leave NSLog() calls in my final,
released product?
Yes, they will clutter up the end users system log -- try to open the
program "Console", this is stdout for GUI programs, and should
preferably only contain serious errors and not verbose run-time info
(because that makes it very difficult to find the error statements).
They don't seem to slow it down any. The advantage is that, if I ever
get a
bug report from a user, I can simply have them launch it from
Terminal, send
me the output, and I can probably tell where the problem is.
E.g. check for some debug property in your environment, then the user
can still do so, but he'll have to launch your application with a
debug-argument, setting an environment-variable or similar...
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.