| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
(C) API, and will likely grow further in this direction in the future.
llvm-svn: 102779
|
|
|
|
| |
llvm-svn: 101059
|
|
|
|
|
|
| |
having overloaded functions with inverse semantics.
llvm-svn: 96155
|
|
|
|
| |
llvm-svn: 96145
|
|
|
|
|
|
|
|
|
| |
see it. Instead, translate the locations up-front when we create a
CXSourceRange.
- This is part of a move to make CXSourceRange a pure half-open range, which is
a more natural API for clients to deal with. More cleanups to follow.
llvm-svn: 96144
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
clients can format diagnostics as they wish rather than having to
parse standard error. All of the important parts of the front end's
diagnostics are exposed: text, severity, location, source ranges, and
fix-its. The diagnostics callback is now available with
clang_createTranslationUnitFromSource() and
clang_createTranslationUnit().
As part of this change, CXSourceLocation and CXSourceRange got one
pointer larger, since we need to hold on to the SourceManager and
LangOptions structures in the source location. This is the minimum
amount of information needed for the functions that operate on source
locations and ranges (as implemented now). Previously we held on to
the ASTContext, but the diagnostics callback can end up with source
locations when there is no ASTContext (or preprocessor).
Still to do:
- Code completion needs to support the diagnostics callback, once we
have the ability to (de-)serialize diagnostics.
- Eliminate the "displayDiagnostics" argument to createIndex; we'll
always pass diagnostics to the callback and let it deal with display.
llvm-svn: 94709
|
|
|
|
|
|
| |
range. The token-annotation function does nothing, yet.
llvm-svn: 94551
|
|
back) to a separate header file.
llvm-svn: 94462
|