------- Comment #13 from gdr at integrable-solutions dot net 2005-12-03 01:02 ------- Subject: Re: exception_defines.h #defines try/catch
"hhinnant at apple dot com" <[EMAIL PROTECTED]> writes: | (In reply to comment #8) | > Subject: Re: exception_defines.h #defines try/catch | > | > "hhinnant at apple dot com" <[EMAIL PROTECTED]> writes: | > | > | ------- Comment #5 from hhinnant at apple dot com 2005-12-02 19:07 ------- | > | (In reply to comment #2) | > | > I'd rather you work around this in objective-c or objective c++. | > | | > | How? I'm open to suggestions. | > | > #undef them if you intend to include libstdc++ files and use try/catch | > with funny characters to mean something else with -fno-exceptions? | | I'm sorry, I'm just not understanding what you're suggesting. If you could | expound on your suggestion I would be most appreciative. If it helps, here is | a demo file that I would like to have work with -fno-exceptions. I'm saying that if you're intending to use try/catch and yet not want what the mean in standard C++, nor what they would mean in GNU C++ with -fno-exceptions, then you have to watch what you're doing. Meaning, in your *own* codes, you #undef try/catch. Whether it is in Cocoa.h or foobar.c, I don't care. Just take your responsability to #undef them -- because you have decided to have mean something else. I'm not inclined in seeing the libstdc++ be uglified in that direction. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25191
