On 11/11/2015 11:45 PM, Iain Buclaw via Digitalmars-d wrote:
> Nor do I believe we need to catch C++ objects with catch(...). Catching C++
objects will need an explicit catch(std.exception*).
>
Well, as demonstrated, that is the one thing that can be supported now for
free. Either by allowing C++-style catch-all or using language specific
catch-all class matching.
I don't agree with implementing things just because we can. There has to be a
good case for it. I cannot see a case for catching ints, strings, etc. My
understanding is that this is more or less acknowledged by the C++ community,
and std::exceptions are used.
Any type could be caught, again I demonstrated this, but I would have more
confidence if g++ generated the typeinfo bindings for us using pragma(mangle) to
some D-friendly symbol. Rather than us pushing in more frail mangling support
from our end.
Having dealt with mangling issues for decades, I'm not overly concerned about
it.
