From e74606fd0847fbc5859f52ef03ddca1e2c2a29ef Mon Sep 17 00:00:00 2001 From: Bas Leijdekkers Date: Thu, 14 Oct 2010 13:29:34 +0200 Subject: [PATCH] clarify "log statement not guarded by log condition" inspection description --- .../LogStatementGuardedByLogCondition.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/plugins/InspectionGadgets/src/inspectionDescriptions/LogStatementGuardedByLogCondition.html b/plugins/InspectionGadgets/src/inspectionDescriptions/LogStatementGuardedByLogCondition.html index c822ddc947b1..acd2e2b0029e 100644 --- a/plugins/InspectionGadgets/src/inspectionDescriptions/LogStatementGuardedByLogCondition.html +++ b/plugins/InspectionGadgets/src/inspectionDescriptions/LogStatementGuardedByLogCondition.html @@ -1,8 +1,9 @@
-This inspection reports any log statements which are not surrounded by a guard -condition. The evaluation of the argument(s) of a log statement can be expensive. +This inspection reports log statements with non-constant arguments which are not +surrounded by a guard condition. +The evaluation of the arguments of a log statement can be expensive. Surrounding a log statement with a guard clause prevents that cost when the logging is disabled for the level used by the logging statement. This is especially for the least serious level (trace, debug, finest) of logging statements, because those are