This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/25191] exception_defines.h #defines try/catch
- From: "gdr at cs dot tamu dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Jan 2006 01:10:42 -0000
- Subject: [Bug libstdc++/25191] exception_defines.h #defines try/catch
- References: <bug-25191-11686@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #30 from gdr at cs dot tamu dot edu 2006-01-12 01:10 -------
Subject: Re: exception_defines.h #defines try/catch
"hhinnant at apple dot com" <gcc-bugzilla@gcc.gnu.org> writes:
| (In reply to comment #28)
| > Subject: Re: exception_defines.h #defines try/catch
| >
| > | No, "try" in this context is not a keyword.
| >
| > I did not say it was a keyword. I know what it is in that phase.
| >
| > try/catch are special when -fno-exceptions.
|
| In the preprocess stage, try/catch are not special when -fno-exceptions
| according to the compiler.
They are for libstdc++. You can debate at length. You won't change
that fundamental fact. However, you'll make progress, when you
recognize that and solve the problem where it should be.
[...]
| I realize that once the customer specifies -fno-exceptions, all bets
| are off.
Great. Fix the problem in the front-end.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25191