5 Commits

Author	SHA1	Message	Date
Douglas Gregor	29d907de03	When we run into an error parsing or type-checking the left-hand side ... of a binary expression, continue on and parse the right-hand side of the binary expression anyway, but don't call the semantic actions to type-check. Previously, we would see the error and then, effectively, skip tokens until the end of the statement. The result should be more useful recovery, both in the normal case (we'll actually see errors beyond the first one in a statement), but it also helps code completion do a much better job, because we do "real" code completion on the right-hand side of an invalid binary expression rather than completing with the recovery completion. For example, given x = p->y if there is no variable named "x", we can still complete after the p-> as a member expression. Along the recovery path, we would have completed after the "->" as if we were in an expression context, which is mostly useless. llvm-svn: 114225	2010-09-17 22:25:06 +00:00
Chris Lattner	0073962025	when emitting an error about a missing } in a compound statement, emit ... a "to match this {" note, pointing out the opener. llvm-svn: 112709	2010-09-01 15:49:26 +00:00
Daniel Dunbar	8fbe78f6fc	Update tests to use %clang_cc1 instead of 'clang-cc' or 'clang -cc1'. ... - This is designed to make it obvious that %clang_cc1 is a "test variable" which is substituted. It is '%clang_cc1' instead of '%clang -cc1' because it can be useful to redefine what gets run as 'clang -cc1' (for example, to set a default target). llvm-svn: 91446	2009-12-15 20:14:24 +00:00
Fariborz Jahanian	0399c1c9c0	Change tests to use clang -cc1... ... llvm-svn: 91297	2009-12-14 17:36:25 +00:00
Fariborz Jahanian	18f4107eb7	test case for my last patch. ... llvm-svn: 80382	2009-08-28 17:53:05 +00:00