[cpp-threads] Slightly revised memory model proposal (D2300)
Nick Maclaren
nmm1 at cus.cam.ac.uk
Wed Jun 6 11:08:32 BST 2007
"Alexander Terekhov" <alexander.terekhov at gmail.com> wrote:
>
> > or SIGFPE) and SIGSEGV etc.
>
> These are synchronous (not asynchronous) signals which C++
> implementations are free to translate to C++ exceptions. Don't get me
> started on std::unexpected() and C++ EH/ES, contact Dimov and/or
> Abrahams.
Yes and no. They AREN'T always synchronous, in the absence of special
action (usually extra compiled code) to make them so. Programming
handlers that are intended to throw C++-style exceptions when they
aren't fully synchronous is, er, interesting.
Regards,
Nick Maclaren,
University of Cambridge Computing Service,
New Museums Site, Pembroke Street, Cambridge CB2 3QH, England.
Email: nmm1 at cam.ac.uk
Tel.: +44 1223 334761 Fax: +44 1223 334679
More information about the cpp-threads
mailing list