"Well, in the case of undefined behaviour the compiler is free to do what it wants, so that reasoning would apply to every other feature of C++ as well."
Yes. That's entirely in keeping with what I said.
So the circumstances under which terminate can be called are at least a list of 8 things in the spec, plus whatever undefined things the compiler feels like.
So that would be my original "slightly ill-defined" statement.
You see, and now I'm wondering if I should go get a head MRI because I'm under this impression that I'm writing English in reasonably complete sentences.
Given unexpected() why is there a terminate()
Quote:Original post by Bregma
Your use of the present tense in that sentence is ill-advised, since you mean "may or may not be removed by the time the next generation but one are confused by it."
That's right. What I'm getting at is that exception specifications will go away and are presently rarely used anyway (as hinted at by that document), so IMHO, as an application writer, it is reasonable to not bother with them at all until they will go away for good.
Quote:Original post by Katie
You see, and now I'm wondering if I should go get a head MRI because I'm under this impression that I'm writing English in reasonably complete sentences.
Everyone wonders about this after witnessing Sneftel talking about C++. ;)
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement