hanchenye-llvm-project/clang
Douglas Gregor 2c8bd47a6a When the # of top-level declarations changes after reparsing a
translation unit, refresh code-completion results because they've
probably changed. However, enforce a cooldown period between
refreshes, to avoid thrashing.

llvm-svn: 111218
2010-08-17 00:40:40 +00:00
..
INPUTS
bindings/python
clang.xcodeproj Update Xcode project 2010-08-12 20:53:33 +00:00
docs Update UsersManual, we support '#pragma align' now. 2010-08-02 15:36:37 +00:00
examples Remove wpa 'example', it isn't being maintained. 2010-08-11 15:21:41 +00:00
include When the # of top-level declarations changes after reparsing a 2010-08-17 00:40:40 +00:00
lib When the # of top-level declarations changes after reparsing a 2010-08-17 00:40:40 +00:00
runtime Runtime: Always build compiler-rt using the Clang we just built, instead of the 2010-06-30 22:10:41 +00:00
test A field of incomplete type is sufficiently disruptive that we should mark 2010-08-16 23:42:35 +00:00
tools Extend the code-completion caching infrastructure to include global 2010-08-15 06:18:01 +00:00
utils Fix typo in test program 2010-07-14 00:09:17 +00:00
www Update documentation regarding use of 'class' in 2010-08-11 18:57:26 +00:00
CMakeLists.txt clang: Derive version name from LLVM unless specified explicitly. This means 2010-06-25 23:34:47 +00:00
INSTALL.txt
LICENSE.TXT
Makefile Move lib/Runtime to runtime/, and build after everything else. 2010-06-30 22:10:38 +00:00
ModuleInfo.txt
NOTES.txt A Release-Asserts build is now called a Release build. 2010-07-07 07:49:17 +00:00
README.txt Fix typo (test commit) 2010-06-17 12:39:05 +00:00
TODO.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.cs.uiuc.edu/mailman/listinfo/cfe-dev

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