aboutsummaryrefslogtreecommitdiff
path: root/test/Parser/cxx-try.cpp
diff options
context:
space:
mode:
authorSebastian Redl <sebastian.redl@getdesigned.at>2009-04-26 21:08:36 +0000
committerSebastian Redl <sebastian.redl@getdesigned.at>2009-04-26 21:08:36 +0000
commitde1b60a9868f80f0872ed05d78df3b40a10ba5ca (patch)
treec2c08ef516f19e1833eb717cb80a424f7e3fad6c /test/Parser/cxx-try.cpp
parentb9fa917e90d5d70d2d84c8cb7e7470b3828f957d (diff)
The mysterious bug turns out to be an incredibly bone-headed mistake.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@70160 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/Parser/cxx-try.cpp')
-rw-r--r--test/Parser/cxx-try.cpp5
1 files changed, 1 insertions, 4 deletions
diff --git a/test/Parser/cxx-try.cpp b/test/Parser/cxx-try.cpp
index 8deed35559..535f40d780 100644
--- a/test/Parser/cxx-try.cpp
+++ b/test/Parser/cxx-try.cpp
@@ -30,14 +30,11 @@ void h() try {
struct A {
int i;
- A(float) : i(0) try {} // expected-error {{expected '{' or ','}}
A(int);
A(char);
- // FIXME: There's something very strange going on here. After the first
- // inline function-try-block, subsequent inline bodies aren't parsed anymore.
- // Valgrind is silent, though, and I can't even debug this properly.
A() try : i(0) {} catch(...) {}
void f() try {} catch(...) {}
+ A(float) : i(0) try {} // expected-error {{expected '{' or ','}}
};
A::A(char) : i(0) try {} // expected-error {{expected '{' or ','}}