Hi. Thank you for the replies, I figured I might be the only one pedantic about it and am relieved to see it's not the case.
I'll do some tests and post the results if meaningful. Best regards, Ewald On 9 July 2012 11:42, Michael Wiles <[email protected]> wrote: > And it's probably good practice to have a blanket policy of _always_ have > the code guard. Regardless of the logging level. Once you get passed 3 > people in your team you want to simplify code conventions. > > The other problem is that when you change something from error to info or > something people might not realise they need to put the if in and so you > might get some logging statements which are not wrapped. You want to avoid > that. > > > On 9 July 2012 11:39, Dr Heinz M. Kabutz <[email protected]> wrote: >> >> The String is first constructed and then passed into the log() method. So >> yeah, you should use code guards (if (log.isDebugEnabled()) etc.) when you >> write logging statements. >> >> Regards >> >> Heinz >> -- >> Dr Heinz M. Kabutz (PhD CompSci) >> Author of "The Java(tm) Specialists' Newsletter" >> Sun Java Champion >> IEEE Certified Software Development Professional >> http://www.javaspecialists.eu >> Tel: +30 69 75 595 262 >> Skype: kabutz >> >> -- You received this message because you are subscribed to the Google Groups "CTJUG Tech" 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/CTJUG-Tech?hl=en For Cape Town Java User Group home page see http://www.ctjug.org.za/ For jobs see http://jobs.gamatam.com/
