3 ms·
The problem with exception-less C++ is that new, delete, ctors, and dtors become timebombs when they fail in a way that would have generated an exception.
by kevin_thibedeau 7y ago
The problem with exception-less C++ is that new, delete, ctors, and dtors become timebombs when they fail in a way that would have generated an exception.
- keldaris 7y agoI'm not sure why you were downvoted. I almost exclusively write exception-less C++ (compiling everything with "-fno-exceptions"), but correctly handling errors in constructors and destructors is absolutely an important concern. It's not hard to do, obviously, but it does require forethought and heavily encourages delegating complex logic to other parts of the code.
- heinrich5991 7y agodtors that throw come with their own share of problems: If they do so while another exception is in flight (dtors are still called for objects when the stack is being unwound(?)), C++ crashes the process.
- NikkiA 7y agoIf new fails your program crashing is probably going to be the only outcome anyway, might as well fail from an unhandled exception. And if you're putting things that can throw exceptions in your ctors or dtors you're probably already writing code that is a timebomb