catch(...) and forced unwind

[Geoff Keating]

Jason Merrill <jason@redhat.com> writes:

> On Tue, 16 Dec 2003 18:55:13 -0500, David Abrahams <dave@boost-consulting.com> wrote:
> 
> > Matt Austern <austern@apple.com> writes:
> >
> >> The real issue, of course is the old one: that the people defining the
> >> POSIX standard and the people defining the C++ standard didn't
> >> spend enough time talking to each other.  POSIX doesn't know
> >> anything about C++ contracts.
> 
> > Nor about standard C++ library functions, I presume?  Why should it
> > have any impact on the behavior of the C++ lib from a standards POV?
> 
> The two standards are incompatible as written.  To make pthreads and C++
> play nice together, one or both need some adjustment.

That's not really correct, though, is it?  You can't write a strictly
conforming C++ program that uses threads.  Pthreads doesn't impose any
requirements on C++ code when pthreads is not used.  Thus, the
standards do not conflict.

-- 
- Geoffrey Keating <geoffk@geoffk.org>