On Friday, 12 September 2014 at 06:56:29 UTC, Jacob Carlborg
wrote:
On 12/09/14 05:25, deadalnix wrote:
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.
On 64bit Objective-C can catch C++ exceptions. But I don't
think you can do anything with the exception, i.e. it uses the
following catch syntax:
@catch(...) {}
Would that be easier?
Yes, but still require the D runtime to interface with the C++
runtime, in order to restore the proper context.
