[NFC] Remove ASCII lines from comments

A lot of comments in LLDB are surrounded by an ASCII line to delimit the
begging and end of the comment.

Its use is not really consistent across the code base, sometimes the
lines are longer, sometimes they are shorter and sometimes they are
omitted. Furthermore, it looks kind of weird with the 80 column limit,
where the comment actually extends past the line, but not by much.
Furthermore, when /// is used for Doxygen comments, it looks
particularly odd. And when // is used, it incorrectly gives the
impression that it's actually a Doxygen comment.

I assume these lines were added to improve distinguishing between
comments and code. However, given that todays editors and IDEs do a
great job at highlighting comments, I think it's worth to drop this for
the sake of consistency. The alternative is fixing all the
inconsistencies, which would create a lot more churn.

Differential revision: https://reviews.llvm.org/D60508

llvm-svn: 358135

1 files changed, 0 insertions, 10 deletions

diff --git a/lldb/unittests/Utility/StreamTest.cpp b/lldb/unittests/Utility/StreamTest.cpp
index 0514625b99f..2e2bcb344fc 100644
--- a/lldb/unittests/Utility/StreamTest.cpp
+++ b/lldb/unittests/Utility/StreamTest.cpp
@@ -279,9 +279,7 @@ TEST_F(StreamTest, PutMaxHex64ByteOrderLittle) {
   EXPECT_EQ("12341278563412efcdab9078563412", TakeValue());
 }
 
-//------------------------------------------------------------------------------
 // Shift operator tests.
-//------------------------------------------------------------------------------
 
 TEST_F(StreamTest, ShiftOperatorChars) {
   s << 'a' << 'b';
@@ -345,9 +343,7 @@ TEST_F(StreamTest, PutPtr) {
 // that it should use the host byte order.
 const static auto hostByteOrder = lldb::eByteOrderInvalid;
 
-//------------------------------------------------------------------------------
 // PutRawBytes/PutBytesAsRawHex tests.
-//------------------------------------------------------------------------------
 
 TEST_F(StreamTest, PutBytesAsRawHex8ToBigEndian) {
   uint32_t value = 0x12345678;
@@ -405,9 +401,7 @@ TEST_F(StreamTest, PutRawBytesToMixedEndian) {
 #endif
 }
 
-//------------------------------------------------------------------------------
 // ULEB128 support for binary streams.
-//------------------------------------------------------------------------------
 
 TEST_F(BinaryStreamTest, PutULEB128OneByte) {
   auto bytes = s.PutULEB128(0x74ULL);
@@ -493,9 +487,7 @@ TEST_F(BinaryStreamTest, PutULEB128One) {
   EXPECT_EQ(1U, bytes);
 }
 
-//------------------------------------------------------------------------------
 // SLEB128 support for binary streams.
-//------------------------------------------------------------------------------
 
 TEST_F(BinaryStreamTest, PutSLEB128OneByte) {
   auto bytes = s.PutSLEB128(0x74LL);
@@ -581,9 +573,7 @@ TEST_F(BinaryStreamTest, PutSLEB128One) {
   EXPECT_EQ(1U, bytes);
 }
 
-//------------------------------------------------------------------------------
 // SLEB128/ULEB128 support for non-binary streams.
-//------------------------------------------------------------------------------
 
 // The logic for this is very simple, so it should be enough to test some basic
 // use cases.