Subject: Re: [ub] Draft 1 of Stackable, Thread Local, Signal Guards
From: Peter C++ (peter.cpp_at_[hidden])
Date: 2019-05-31 03:07:11
The code uses something called bitfiel in line 4 and 25. is that just an enum class?
Also, why does the design use virtual functions? If it is about platform differences, this is a compile time issue and not run time.
Sent from Peter Sommerlad's iPad
+41 79 432 23 32
> On 30 May 2019, at 17:51, Niall Douglas <s_sourceforge_at_[hidden]> wrote:
> Dear SG12,
> CC: Herb Sutter
> As we limber up to the Cologne mailing deadline, here is draft 1 of a
> proposal to add stackable, thread local, signal guards to the C++
> standard library. It will be submitted for SG12 to review at Cologne.
> A signal guard allows one to recover from a hardware exception during a
> guarded piece of code e.g. SIGFPE, SIGSEGV, and so on. The guard acts on
> the local thread, rather than globally. And they can be stacked, one
> inside another.
> They also can guard against OOM and termination, which may be useful for
> Herbceptions' proposed OOM handling changes.
> A reference library implementation is linked, it's been in production
> for over a year now, and has proven quite popular with many people as it
> abstracts away lots of annoying implementation specifics.
> Comments welcome.
> <20190530 draft 1 Stackable thread local signal guards.pdf>
> ub mailing list
SG12 list run by herb.sutter at gmail.com