Re: Leave NSLog()s in Final Product?
Re: Leave NSLog()s in Final Product?
- Subject: Re: Leave NSLog()s in Final Product?
- From: Bill Cheeseman <email@hidden>
- Date: Fri, 12 Mar 2004 12:04:43 -0500
on 2004-03-12 10:20 AM, Piers Uso Walter at email@hidden wrote:
>
I would advise to use NSLog() just for logging
>
of serious bugs where recovery is not possible. All other output could
>
be encapsulated by a wrapper function that normally does nothing, but
>
calls NSLog() when the application was started with a -debug command
>
line switch.
I take a slightly different view on this. I leave in those NSLog calls that
generate information that might be useful to a user of my app. I mention
this in the documentation, telling the user to launch Console.app if they're
having certain kinds of problems.
For example, I have a faceless background app that runs AppleScripts written
by the user. I can't put up a dialog when the user's script is written
incorrectly, because mine is a faceless app. But I can and do log the
AppleScript error information so the scripter can see it in Console.app.
Scripters are used to seeing this error information when they debug their
own scripts in a script editor, so they expect to have it available and it
isn't too mysterious for them.
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
The AppleScript Sourcebook -
http://www.AppleScriptSourcebook.com
Vermont Recipes -
http://www.stepwise.com/Articles/VermontRecipes
_______________________________________________
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.