mattreecebentley
commented
1 year ago My understanding is that if exceptions are disabled, then the code will compile, but the compiler will not include the code in the catch blocks, or throw statements. Otherwise games which don't use exceptions wouldn't work with anything that did, including STD:: stuff and OS stuff. Obviously the upshot of what this means is going to vary from compiler to compiler, as disabling exceptions is outside of the C++ standard behaviour, see here: https://stackoverflow.com/questions/943087/what-exactly-will-happen-if-i-disable-c-exceptions-in-a-project for MSVC and here: https://stackoverflow.com/questions/45935978/what-happens-when-code-that-throws-exceptions-is-linked-against-a-library-compil for GCC.
As long as the user doesn't do anything stupid (over-allocate memory, etc) in colony they won't encounter exceptions. If they do, there is no way of handling these with error codes instead as allocator_traits::construct doesn't have a return value, only exceptions, and it is required for allocator support, so malloc etc aren't appropriate.
If you've got a specific compiler/situation where colony is causing problems in this scenario (exceptions turned off) please tell me and I'll look into it.
[UPDATE: okay, compiled with -fno-exceptions under GCC shows me the problem, at least for GCC. Will look into it. GCC has the __EXCEPTIONS flag, possibly clang as well, I think MSVC compiles exceptions code fine when exceptions are disabled, but will have to check]
sunnlok
AIIleG
Right now exceptions are a fixed part of plf_colony, but many projects have exceptions disabled, especially games. This obviously means that plf_colony will not compile. I was wondering if there was any interest in supporting users that have disabled exceptions via macros for/around try, catch and throw? The length_errors could also be handled via asserts in those cases as well.
Was this a deliberate choice or just never considered? If its deliberate, modifying the source to fit the use case is obviously a valid solution as well, just makes integrating new versions slightly more work.