aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/CommandLine.cpp
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2009-03-27 23:10:48 +0000
committerDouglas Gregor <dgregor@apple.com>2009-03-27 23:10:48 +0000
commit333489bba35d91e4ddb101f441087177c492d090 (patch)
tree6b658646aed7c601a730536e09816cecc7ff0c65 /llvm/lib/Support/CommandLine.cpp
parent669f1d0b0b7ab0fd05f4cf672eab6dbe3f358953 (diff)
downloadllvm-333489bba35d91e4ddb101f441087177c492d090.zip
llvm-333489bba35d91e4ddb101f441087177c492d090.tar.gz
llvm-333489bba35d91e4ddb101f441087177c492d090.tar.bz2
Initial implementation of parsing, semantic analysis, and template
instantiation for C++ typename-specifiers such as typename T::type The parsing of typename-specifiers is relatively easy thanks to annotation tokens. When we see the "typename", we parse the typename-specifier and produce a typename annotation token. There are only a few places where we need to handle this. We currently parse the typename-specifier form that terminates in an identifier, but not the simple-template-id form, e.g., typename T::template apply<U, V> Parsing of nested-name-specifiers has a similar problem, since at this point we don't have any representation of a class template specialization whose template-name is unknown. Semantic analysis is only partially complete, with some support for template instantiation that works for simple examples. llvm-svn: 67875
Diffstat (limited to 'llvm/lib/Support/CommandLine.cpp')
0 files changed, 0 insertions, 0 deletions