aboutsummaryrefslogtreecommitdiff
path: root/www/lldb-coding-conventions.html
diff options
context:
space:
mode:
Diffstat (limited to 'www/lldb-coding-conventions.html')
-rw-r--r--www/lldb-coding-conventions.html28
1 files changed, 14 insertions, 14 deletions
diff --git a/www/lldb-coding-conventions.html b/www/lldb-coding-conventions.html
index 7cd959ccf9de..c3702decb31e 100644
--- a/www/lldb-coding-conventions.html
+++ b/www/lldb-coding-conventions.html
@@ -22,20 +22,20 @@
<p>The LLDB coding conventions differ in a few important respects from LLVM.</p>
- <p>
- Note that <a href="http://clang.llvm.org/docs/ClangFormat.html">clang-format</a> will deal with
- most of this for you, as such is suggested to run on patches before uploading. Note however that
- clang-format is not smart enough to detect instances of humans intentionally trying to line variables
- up on a particular column boundary, and it will reformat them to remove this "extraneous" whitespace.
- While this is usually the correct behavior, LLDB does have many uses of manually aligned types and
- fields, so please be aware of this behavior of clang-format when editing this type of code.
- </p>
- <p>
- <b>Important</b>: Where not explicitly outlined below, assume that the
- <a href="http://llvm.org/docs/CodingStandards.html">LLVM Coding Conventions</a> are to be followed.
- </p>
-
- <h3>Source code width:</h3>
+ <p>
+ Note that <a href="http://clang.llvm.org/docs/ClangFormat.html">clang-format</a> will deal with
+ most of this for you, as such is suggested to run on patches before uploading. Note however that
+ clang-format is not smart enough to detect instances of humans intentionally trying to line variables
+ up on a particular column boundary, and it will reformat them to remove this "extraneous" whitespace.
+ While this is usually the correct behavior, LLDB does have many uses of manually aligned types and
+ fields, so please be aware of this behavior of clang-format when editing this type of code.
+ </p>
+ <p>
+ <b>Important</b>: Where not explicitly outlined below, assume that the
+ <a href="http://llvm.org/docs/CodingStandards.html">LLVM Coding Conventions</a> are to be followed.
+ </p>
+
+ <h3>Source code width:</h3>
<p>lldb does not follow the 80 character line restriction llvm imposes. In our
experience, trying to fit C++ code into an 80 character line results in code that
is awkward to read, and the time spent trying to find good indentation points to