catch(...) and forced unwind
David Abrahams
dave@boost-consulting.com
Wed Dec 17 07:04:00 GMT 2003
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.
Thanks, I gathered someone is saying that. I'm asking someone to
connect the dots for me so I can see what, specifically, makes them
incompatible.
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
More information about the Gcc
mailing list