This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: CLEANUP_POINT_EXPR/WITH_CLEANUP_EXPR vs TRY_CATCH_EXPR
- To: mrs at wrs dot com
- Subject: Re: CLEANUP_POINT_EXPR/WITH_CLEANUP_EXPR vs TRY_CATCH_EXPR
- From: Richard Stallman <rms at gnu dot org>
- Date: Sat, 19 Dec 1998 20:51:47 -0700 (MST)
- CC: kenner at vlsi1 dot ultra dot nyu dot edu, egcs at cygnus dot com, gcc2 at cygnus dot com
- References: <199812190025.QAA09311@kankakee.wrs.com>
- Reply-to: rms at gnu dot org
> That was set up so that a front end that wanted to use EH had to
> call a function in order to do it.
Which is wrong. A language that emits tree codes that map to EH
constructs should just work because the documented semantics of those
tree codes demand it.
I agree. The goal is to make the EH facilities of GCC usable for all
languages. So the feature should always be "on". If a program uses
the EH tree codes, they should do their job.