Thanks, i know that exceptions are not disabled and I think I also understand what noexcept means,
But my discussion was more in the particular case of having say an object is deleted twice in a code where noexcept is used: with no noexcept on it should be captured in this code,
but now it would not break in a debugger in that code with a useful stack, but instead may give you a sub-optimal exception that is not very helpful? (I see system exceptions all the time in the console windows for which I don’t know what to do with i.e. no stack to investigate…)
So my use case and noob question would be to try answer your question:
Is it still going to throw an helpful exception (with a stack maybe) if the code that triggers the delete has a noexcept (so it won’t itself throw an exception) ?
The difference here is I sure can have a system exception in the end telling me that something was wrong but it would not be as helpful as an exception triggered in the code that generated the delete.
That is just an use case example to try to identify a potential need that is more general on noexcept,
that I try to build so that I gain understanding on it.
So that someone could answer would it sometimes be useful or not to be able to disable this noexcept statement once and for all while debugging and then being able to reactivate them once done.
More recently, I come from .net environments where we always have exceptions in the non native code, so even if I do also have a some experience (old knowledge though!) on C++ memory management and exceptions I am not 100% waterproof on that yet so I appreciate feedback and pardon my naive questions!