llvm-capstone/clang
Martin Probst 101ec894c3 clang-format: [JS] Don't indent JavaScript IIFEs.
Because IIFEs[1] are often used like an anonymous namespace around large
sections of JavaScript code, it's useful not to indent to them (which
effectively reduces the column limit by the indent amount needlessly).

It's also common for developers to wrap these around entire files or
libraries. When adopting clang-format, changing the indent entire file
can reduce the usefulness of the blame annotations.

Patch by danbeam, thanks!

Differential Revision: https://reviews.llvm.org/D32989

llvm-svn: 302580
2017-05-09 20:04:09 +00:00
..
bindings Add Python 3 support to clang.cindex 2017-04-20 10:11:01 +00:00
cmake Build the Apple-style stage2 with modules 2017-05-09 17:27:03 +00:00
docs docs: Fix Sphinx detection with out-of-tree builds 2017-05-09 01:42:33 +00:00
examples Add LLVMOption to clang-interpreter, corresponding to r291938. 2017-01-14 08:54:05 +00:00
include [CodeCompletion] Complete platform names in @available expressions 2017-05-09 16:05:04 +00:00
INPUTS
lib clang-format: [JS] Don't indent JavaScript IIFEs. 2017-05-09 20:04:09 +00:00
runtime
test Update testcase for upstream LLVM changes (r302469). 2017-05-09 19:47:41 +00:00
tools [modules] Round-trip -Werror flag through explicit module build. 2017-05-03 00:28:49 +00:00
unittests clang-format: [JS] Don't indent JavaScript IIFEs. 2017-05-09 20:04:09 +00:00
utils utils: Silence -Wpedantic warning 2017-05-01 00:26:59 +00:00
www Implement DR 373 "Lookup on namespace qualified name in using-directive" 2017-03-17 21:41:20 +00:00
.arcconfig
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt [analyzer] Add new Z3 constraint manager backend 2017-04-04 19:52:25 +00:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
ModuleInfo.txt
NOTES.txt
README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source-level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:              http://clang.llvm.org/
Building and using Clang:          http://clang.llvm.org/get_started.html
Clang Static Analyzer:             http://clang-analyzer.llvm.org/
Information on the LLVM project:   http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/