ISO/IEC Standard 14882-2003 (e.g. C++ 2003) Section 1.9.4
"Certain other operations are described in this International Standard as undefined (for example, the effect of dereferencing the null pointer). [Note: this International Standard imposes no requirements on the behavior of programs that contain undefined behavior. ]” > On Dec 2, 2015, at 5:11 PM, Roland King <r...@rols.org> wrote: > >> My understanding is that the C++ spec unequivocally defines this as an error >> and therefor it shouldn’t be happening at all. > > That’s the crux of Jens’ question. Which version of the C++ spec actually > includes wording which makes this undefined behaviour? There’s drafts and > proposals for language which would unarguably make it so, but I haven’t yet > found a version of the specification which currently includes that language. > There’s evidence that members of the C++ working group feel it ought to be > undefined, despite having answered the exact question about its legality in > 2001 saying that yes it’s legal, but it’s not clear they’ve acted on it. > > All hair-splitting in the end. If the compiler you’re using considers it > undefined behaviour then you don’t have a lot of options but to stop using it > if you want to avoid undefined results.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
