------- Comment #5 from pcarlini at suse dot de 2006-07-07 17:17 -------
(In reply to comment #4)
> However, we know that it should be possible to write cancel-safe C++
> libraries (including, in particular, libstdc++); otherwise, it's hard to
> use C++ in a multi-threaded application. And, we know that we can do it
> with a very simple hook: we just need a way to ask whether the current
> thread is being cancelled. GLIBC has lots of extensions; if we can have
> __thread_cancelled(), we've got enough, without having to solve the
> problem of whether or not it should be possible to catch (and not
> rethrow) the thread-cancellation exception. (I'd rather have a name for
> the thread exception, as that seems more natural, but this is a
> difference only of syntax; the hook function would be a perfectly
> satisfactory way to make progress.)
FWIW my personal opinion about this issue, I concur. Now, assuming all the
knowledgeable people do indeed agree, is it really feasible to add such feature
to glibc? Is someone going to ask glibc maintainers opinion?
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pcarlini at suse dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28145
