From: Zachary Turner Date: Thu, 11 Aug 2016 18:10:40 +0000 (+0000) Subject: Modify coding conventions to mention include ordering. X-Git-Tag: llvmorg-4.0.0-rc1~12722 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=fd34ba53e34bfcdffde5fe0c12efab78381e2c73;p=platform%2Fupstream%2Fllvm.git Modify coding conventions to mention include ordering. llvm-svn: 278373 --- diff --git a/lldb/www/lldb-coding-conventions.html b/lldb/www/lldb-coding-conventions.html index c3702de..7196576 100644 --- a/lldb/www/lldb-coding-conventions.html +++ b/lldb/www/lldb-coding-conventions.html @@ -34,7 +34,20 @@ Important: Where not explicitly outlined below, assume that the LLVM Coding Conventions are to be followed.

- +

Include Order:

+

LLDB follows LLVM's include order, + with an addition for LLDB specific headers.

+
    + +
  1. Main Module Header
  2. +
  3. Local/Private Headers
  4. +
  5. lldb/...
  6. +
  7. llvm/...
  8. +
  9. System #includes
  10. +
+

If you encounter existing code that does not follow this ordering, it should not be + taken as an indication that it is ok to not use it. Instead, the surrounding ordering + should be fixed gradually and incrementally.

Source code width:

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