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 integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Dec 2005 19:23:35 -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 #7 from gdr at integrable-solutions dot net 2005-12-02 19:23 -------
Subject: Re: exception_defines.h #defines try/catch
"pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
| Confirmed. This also causes problems in normal C++ code which does:
|
| #include <string>
|
| int f(void);
| int main(void)
| {
| try {
| f();
| }catch (a) {}
| }
|
| Without the include, you get an error but with the include, you don't which
is
| inconstaint behavior.
Indeed. But that is not changing a valid code into something else as
you claimed earlier.
The use of try/catch is part of the contract of -fno-exceptions. If a
determined programmer decides to abuse them beyond reasons, then I
believe he/she gets what he/she gets.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25191