diff options
author | Daniel Jasper <djasper@google.com> | 2013-01-16 16:23:19 +0000 |
---|---|---|
committer | Daniel Jasper <djasper@google.com> | 2013-01-16 16:23:19 +0000 |
commit | 8c5fba9f87f39ff18425747fcea2ac9f364e3cfe (patch) | |
tree | da30ad6d25c09f91f66965835e73af40fe32a56b /clang/lib | |
parent | f40f67af436c33a0c76ead87d23f77d186abd8e4 (diff) | |
download | bcm5719-llvm-8c5fba9f87f39ff18425747fcea2ac9f364e3cfe.tar.gz bcm5719-llvm-8c5fba9f87f39ff18425747fcea2ac9f364e3cfe.zip |
Fix parsing error in conditional expressions.
We used to incorrectly parse
aaaaaa ? aaaaaa(aaaaaa) : aaaaaaaa;
Due to an l_paren being followed by a colon, we assumed it to be part of
a constructor initializer. Thus, we never found the colon belonging to
the conditional expression, marked the line as bing incorrect and did
not format it.
llvm-svn: 172621
Diffstat (limited to 'clang/lib')
-rw-r--r-- | clang/lib/Format/Format.cpp | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/clang/lib/Format/Format.cpp b/clang/lib/Format/Format.cpp index ebf493c628a..22166aa27ab 100644 --- a/clang/lib/Format/Format.cpp +++ b/clang/lib/Format/Format.cpp @@ -886,6 +886,8 @@ public: break; case tok::colon: // Colons from ?: are handled in parseConditional(). + if (Tok->Parent->is(tok::r_paren)) + Tok->Type = TT_CtorInitializerColon; if (ColonIsObjCMethodExpr) Tok->Type = TT_ObjCMethodExpr; break; @@ -894,10 +896,7 @@ public: TT_ObjCMethodSpecifier; if (!parseParens()) return false; - if (CurrentToken != NULL && CurrentToken->is(tok::colon)) { - CurrentToken->Type = TT_CtorInitializerColon; - next(); - } else if (CurrentToken != NULL && ParensWereObjCReturnType) { + if (CurrentToken != NULL && ParensWereObjCReturnType) { CurrentToken->Type = TT_ObjCSelectorStart; next(); } |