History log of /external/clang/tools/libclang/CXSourceLocation.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
e2748288a04cda2e976a3fe859e4334afaf9274a 11-Jan-2013 Argyrios Kyrtzidis <akyrtzi@gmail.com> [libclang] Add some constness in CXSourceLocation and CXSourceRange.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@172261 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/tools/libclang/CXSourceLocation.h
f59edb96b2d0bfe612b732f19519ab84bb995bd4 04-Dec-2012 Chandler Carruth <chandlerc@gmail.com> Sort #include lines for tools/...

Completely automated with sort_includes.py

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@169240 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/tools/libclang/CXSourceLocation.h
4e4d08403ca5cfd4d558fa2936215d3a4e5a528d 11-Mar-2012 David Blaikie <dblaikie@gmail.com> Unify naming of LangOptions variable/get function across the Clang stack (Lex to AST).

The member variable is always "LangOpts" and the member function is always "getLangOpts".

Reviewed by Chris Lattner

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@152536 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/tools/libclang/CXSourceLocation.h
1a9a0bc472ee4fec72ee8be8b575fb66ca600d1b 29-Jun-2010 Ted Kremenek <kremenek@apple.com> Per Doug's suggestion, move check for invalid SourceLocation into
cxloc::translateSourceLocation() (thus causing all clients of this
function to have the same behavior).

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@107101 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/tools/libclang/CXSourceLocation.h
0a76aae8c03cb7dd7bdbe683485560afaf695959 19-Jun-2010 Chris Lattner <sabre@nondot.org> introduce a new CharSourceRange class, and enhance the diagnostics routines
to use them instead of SourceRange. CharSourceRange is just a SourceRange
plus a bool that indicates whether the range has the end character resolved
or whether the end location is the start of the end token. While most of
the compiler wants to think of ranges that have ends that are the start of
the end token, the printf diagnostic stuff wants to highlight ranges within
tokens.

This is transparent to the diagnostic stuff. To start taking advantage of
the new capabilities, you can do something like this:
Diag(..) << CharSourceRange::getCharRange(Begin,End)





git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@106338 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/tools/libclang/CXSourceLocation.h
f51f20fa34654da75d15a9e2a1a0cd2fc0d8603d 30-Apr-2010 Daniel Dunbar <daniel@zuster.org> Rename 'CIndex' to 'libclang', since it has basically become our stable public
(C) API, and will likely grow further in this direction in the future.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@102779 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/tools/libclang/CXSourceLocation.h