[ http://issues.apache.org/jira/browse/NUTCH-309?page=comments#action_12418404 ]
Jerome Charron commented on NUTCH-309: -------------------------------------- Dawid, you know, sed, awk and regex are my friends, so it was not so painful ;-) As I mentionned in a previous mail, it was just a crude pass on logging : A finest one is planned to review log levels and code guards. AspectJ => +1 for using it for logging, but I don't what are the preformance impacts... > Uses commons logging Code Guards > -------------------------------- > > Key: NUTCH-309 > URL: http://issues.apache.org/jira/browse/NUTCH-309 > Project: Nutch > Type: Improvement > Versions: 0.8-dev > Reporter: Jerome Charron > Assignee: Jerome Charron > Priority: Minor > Fix For: 0.8-dev > > "Code guards are typically used to guard code that only needs to execute in > support of logging, that otherwise introduces undesirable runtime overhead in > the general case (logging disabled). Examples are multiple parameters, or > expressions (e.g. string + " more") for parameters. Use the guard methods of > the form log.is<Priority>() to verify that logging should be performed, > before incurring the overhead of the logging method call. Yes, the logging > methods will perform the same check, but only after resolving parameters." > (description extracted from > http://jakarta.apache.org/commons/logging/guide.html#Code_Guards) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
