On Friday, 12 September 2014 at 00:44:10 UTC, David Nadlinger
wrote:
3) is also doable, but of course significantly more annoying
because you need to deal with the internals of the exception
ABI of your C++ compiler. Accessing the exception object is
relatively trivial, ABI and mangling support is slowly coming
anyway, but OTOH handling the exception lifetime correctly
could become somewhat of a headache.
Yes, that is pretty why I limited myself to the "unwind properly
but do not catch" option. This one would require to mess with the
innards of various C++ runtime.