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. Many users who use the
Console probably wouldn't like it to become cluttered with detritus
from spurious log statements. It makes tech support more difficult if
they need to look at their logs for something else, and may confuse
the user -- "What does ....... mean??? Is something wrong?" Just a
thought.
Heartily agree. NSLog output in a released program should be limited
to reporting actual errors with whatever information is available at
that time to locate and diagnose the problem. Any event that's out of
the ordinary is fair game, not just errors. But (almost) any message
that is essentially reporting that an operation worked as intended is
noise.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
