From 8772a07e5a27f5858ed438d32f717c36d2307e3f Mon Sep 17 00:00:00 2001
From: Simon Brandhof <simon.brandhof@gmail.com>
Date: Thu, 23 Feb 2012 10:33:38 +0100
Subject: [PATCH] Improve description of the Checkstyle rule "Trailing Comment"

---
 .../org/sonar/plugins/checkstyle/rules.xml    | 13 +++---
 ...ecks.indentation.TrailingCommentCheck.html | 42 ++++++++++++++++++-
 2 files changed, 48 insertions(+), 7 deletions(-)

diff --git a/plugins/sonar-checkstyle-plugin/src/main/resources/org/sonar/plugins/checkstyle/rules.xml b/plugins/sonar-checkstyle-plugin/src/main/resources/org/sonar/plugins/checkstyle/rules.xml
index 37c17e03d5f..35c03296e42 100644
--- a/plugins/sonar-checkstyle-plugin/src/main/resources/org/sonar/plugins/checkstyle/rules.xml
+++ b/plugins/sonar-checkstyle-plugin/src/main/resources/org/sonar/plugins/checkstyle/rules.xml
@@ -1427,13 +1427,14 @@
     <priority>MINOR</priority>
     <name><![CDATA[Trailing Comment]]></name>
     <configKey><![CDATA[Checker/TreeWalker/TrailingComment]]></configKey>
-
-
-    <param key="format" type="r">
-
+    <param>
+      <key>format</key>
+      <type>r</type>
+      <defaultValue>^[\\s\\}\\);]*$</defaultValue>
     </param>
-    <param key="legalComment" type="r">
-
+    <param>
+      <key>legalComment</key>
+      <type>r</type>
     </param>
   </rule>
 
diff --git a/plugins/sonar-l10n-en-plugin/src/main/resources/org/sonar/l10n/checkstyle/com.puppycrawl.tools.checkstyle.checks.indentation.TrailingCommentCheck.html b/plugins/sonar-l10n-en-plugin/src/main/resources/org/sonar/l10n/checkstyle/com.puppycrawl.tools.checkstyle.checks.indentation.TrailingCommentCheck.html
index 0296f30b6ad..1a58f64f62d 100644
--- a/plugins/sonar-l10n-en-plugin/src/main/resources/org/sonar/l10n/checkstyle/com.puppycrawl.tools.checkstyle.checks.indentation.TrailingCommentCheck.html
+++ b/plugins/sonar-l10n-en-plugin/src/main/resources/org/sonar/l10n/checkstyle/com.puppycrawl.tools.checkstyle.checks.indentation.TrailingCommentCheck.html
@@ -1 +1,41 @@
-The check to ensure that requires that comments be the only thing on a line.
\ No newline at end of file
+<p>
+  The check to ensure that requires that comments be the only thing on a line. For the case of // comments that means that the only thing that should precede it is whitespace. It
+  doesn't check comments if they do not end line, i.e. it accept the following: Thread.sleep( 10 &lt;some comment here&gt; ); Format property is intended to deal with the "} //
+  while" example.
+</p>
+<p>
+  Rationale: Steve McConnel in "Code Complete" suggests that endline comments are a bad practice. An end line comment would be one that is on the same line as actual code. For
+  example:
+</p>
+<pre>
+  <code>
+    a = b + c; // Some insightful comment
+    d = e / f; // Another comment for this line
+  </code>
+</pre>
+
+<p>
+  Quoting "Code Complete" for the justfication:
+</p>
+<ul>
+  <li>"The comments have to be aligned so that they do not interfere with the visual structure of the code. If you don't align them neatly, they'll make your listing look like it's
+    been through a washing machine."
+  </li>
+  <li>"Endline comments tend to be hard to format...It takes time to align them. Such time is not spent learning more about the code; it's dedicated solely to the tedious task of
+    pressing the spacebar or tab key."
+  </li>
+  <li>"Endline comments are also hard to maintain. If the code on any line containing an endline comment grows, it bumps the comment farther out, and all the other endline comments
+    will have to bumped out to match. Styles that are hard to maintain aren't maintained...."
+  </li>
+  <li>"Endline comments also tend to be cryptic. The right side of the line doesn't offer much room and the desire to keep the comment on one line means the comment must be short.
+    Work
+    then goes into making the line as short as possible instead of as clear as possible. The comment usually ends up as cryptic as possible...."
+  </li>
+  <li>"A systemic problem with endline comments is that it's hard to write a meaningful comment for one line of code. Most endline comments just repeat the line of code, which
+    hurts
+    more than it helps."
+  </li>
+</ul>
+<p>
+  His comments on being hard to maintain when the size of the line changes are even more important in the age of automated refactorings.
+</p>
\ No newline at end of file
-- 
2.39.5