2 ms·
> On the flipside, any serious gamedev C++ FFI must accomodate exceptions-disabled environments Any C++ ffi that accommodates exception also accommodates excep
by CyberRabbi 6y ago
> On the flipside, any serious gamedev C++ FFI must accomodate exceptions-disabled environments
Any C++ ffi that accommodates exception also accommodates exception-disabled environments by virtue of accommodating function calls. Certainly AutoCXX accommodates codebases that use exceptions as well as those that disable exceptions by convention.
- MaulingMonkey 6y ago> Certainly AutoCXX accommodates codebases that [...] disable exceptions by convention. From the documentation, it sounds like that's only true if you eschew Result, the absolute backbone of not-automatically-unwinding Rust error handling. You could presumably, technically, roll your own Rust struct/enum - "NonStdResult" - and expose that to C++ however cxx deigns to expose Rust enums to C++. But that seems... very awkward at best, to completely counter to the entire point of AutoCXX - in trying to eliminate the need to write a bunch of special case conversion boilerplate - at worst. If you're suggesting that as a superior design choice, we're seriously going to have to agree to disagree.