Please do remove them. They make your app larger, slower to run (can be SIGNIFICANTLY slower because of the work Java ends up doing building strings), and... for people working on the platform having an app spewing logs is super annoying, since it buries any -interesting- messages that other parts of the system print.
Actually if I see an app I have installed spewing logs, I will often uninstall it because it is so annoying and greatly reduces the amount of information available in the log if I need to track down something going wrong with my device. Fyi, it is very easy to conditionally compile them -- just define a static final boolean DOLOG = false value, and check that before each log. The Java compiler will strip all of that code out when the constant is false. On Mon, Jul 27, 2009 at 9:01 PM, Maps.Huge.Info (Maps API Guru) < [email protected]> wrote: > > I've been working on an app for a couple of months, it's loaded with > log statements (android.util.Log) now and they are very useful. > > Question: Is it better to remove log statements before deploying to > the market or can they be left in? Are there good reasons to remove > them regardless? > > Thanks in advance. > > -John Coryat > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
