• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Leave NSLog()s in Final Product?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Leave NSLog()s in Final Product?


  • Subject: Re: Leave NSLog()s in Final Product?
  • From: Michael Becker <email@hidden>
  • Date: Fri, 12 Mar 2004 15:45:25 +0100

Is there any reason why I should not leave NSLog() calls in my final,
released product?

IMHO it's okay to leave NSLog()'s in a released product, as long as you have them output useful, well-formatted data. Outputs like "------ initWithFrame: GETS CALLED" followed by "value of variable myName: John Doe" should not appear :-)

Do these NSLog() calls do anything when an application is not launched from
Terminal?

AFAIK, NSLog() always writes to a log-file, I've forgotten which one, but NSLog()'s output should always be accessible, no matter how the application was launched.

Just my 2 cents :-)

- Michael
_______________________________________________
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.


References: 
 >Leave NSLog()s in Final Product? (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Including headers from unix library
  • Next by Date: Drawing a Subclass of NSButton
  • Previous by thread: Leave NSLog()s in Final Product?
  • Next by thread: Re: Leave NSLog()s in Final Product?
  • Index(es):
    • Date
    • Thread