[Bug libstdc++/25191] exception_defines.h #defines try/catch

["bkoz at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #20 from bkoz at gcc dot gnu dot org  2005-12-07 19:01 -------
>  I have customers using Obj C++ who want to turn off C++
> exception support, but retain Obj C exception support.  [snip]

What does this even mean? Can you detail or explain how this is supposed to
work?

> They are not trying to use C++ try/catch in a bizarre or unsupported manner.
> They are simply trying to use ObjC++ exceptions without the unwanted cost of
> C++ exceptions.

IMHO, yes, this is completely misguided, unsupported, bizarre, known to fail,
and should be documented as such.

If you are going to go through and add in hacks to deal with -fno-exceptions
for every C++/X language combo, then I'd be in favor of -fno-exceptions be
changed so that the C++ FE takes care of the keywords, since at least then
it'll all be taken care of in one place and would be consistently well-defined.
I think that's the proper place to fix this.

Can you point out where Objective C++ -fno-exceptions behavior documented?

-benjamin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25191