This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: catch(...) and forced unwind
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Jason Merrill <jason at redhat dot com>, David Abrahams <dave at boost-consulting dot com>, Matt Austern <austern at apple dot com>, Ulrich Drepper <drepper at redhat dot com>, gcc at gcc dot gnu dot org, Richard Henderson <rth at redhat dot com>, Nathan Myers <ncm at cantrip dot org>, Jakub Jelinek <jakub at redhat dot com>, wekempf at cox dot net, fjh at cs dot mu dot oz dot au, Benjamin Kosnik <bkoz at redhat dot com>, William Kempf <williamkempf at hotmail dot com>
- Date: 17 Dec 2003 17:58:15 +0100
- Subject: Re: catch(...) and forced unwind
- Organization: Integrable Solutions
- References: <xypwu91ofvf.fsf@miranda.boston.redhat.com><ud6at1wvg.fsf@boost-consulting.com><xypekv9nr9u.fsf@miranda.boston.redhat.com><u65gkyhv4.fsf@boost-consulting.com><20031214035909.GE2416@tofu.dreamhost.com><xypk74xltaa.fsf@miranda.boston.redhat.com><ullpdlksl.fsf@boost-consulting.com><xyp1xr5lh5q.fsf@miranda.boston.redhat.com><usmjlhryu.fsf@boost-consulting.com><278A5A0A-3001-11D8-8564-00039390D9E0@apple.com><usmjkbkb5.fsf@boost-consulting.com><0BB52C3C-3009-11D8-8564-00039390D9E0@apple.com><ud6aobfgy.fsf@boost-consulting.com><A156A7B0-3012-11D8-8564-00039390D9E0@apple.com><uu1409v32.fsf@boost-consulting.com><xypd6aoi0zz.fsf@miranda.boston.redhat.com><1071632782.3793.114.camel@minax.codesourcery.com><xypk74wgc3b.fsf@miranda.boston.redhat.com><1071647478.3847.19.camel@minax.codesourcery.com>
Mark Mitchell <mark@codesourcery.com> writes:
| > There's still the question of what to do with pthread_exit.
|
| The consistent thing would seem to be to have it throw
| "posix::thread_exit". (This, by the way, is analagous to the Python
| idea that "return" statements are equivalent to throwing a special kind
| of exception.)
Yeah, that might be fine for Python and other languages like ML that
use exceptions to return value. But, I would strongly recommend
against introducing that slippery slope in C++, C++ libraries.
-- Gaby