From fdba3aba0a17395abfe92afd1f739fc6a61c9266 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Fri, 19 Mar 2010 12:04:39 -0700 Subject: Let try_block contain any statement We still require the block for parsing, but the optimizer likes to fold singleton blocks away, so any statement is possible. PR11341 masks such issues at compile time, but I'm a little surprised that we've gotten away with this at runtime... --- staptree.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/staptree.h b/staptree.h index 67349b8e..284b4ea1 100644 --- a/staptree.h +++ b/staptree.h @@ -529,8 +529,8 @@ struct block: public statement struct try_block: public statement { - block* try_block; // may be 0 - block* catch_block; // may be 0 + statement* try_block; // may be 0 + statement* catch_block; // may be 0 symbol* catch_error_var; // may be 0 void print (std::ostream& o) const; void visit (visitor* u); -- cgit