Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wrong example of unspecified behavior in [intro.abstract]/3 #1742

Closed
timsong-cpp opened this issue Sep 9, 2017 · 2 comments
Closed

Wrong example of unspecified behavior in [intro.abstract]/3 #1742

timsong-cpp opened this issue Sep 9, 2017 · 2 comments
Assignees
@jensmaurer
Labels
cwg Issue must be reviewed by CWG.
Milestone
C++20 IS

Comments

@timsong-cpp
Copy link
Contributor

timsong-cpp commented Sep 9, 2017 •
edited

Certain other aspects and operations of the abstract machine are described in this International Standard as unspecified (for example, evaluation of expressions in a new-initializer if the allocation function fails to allocate memory ([expr.new])).

The example is no longer correct after P0145.
@jensmaurer
Copy link
Member

jensmaurer commented Sep 15, 2017 •
edited

CWG 1583 changed the example to the current wording. Since it was previously updated by a core issue, I guess we shouldn't do it editorially this time. I've sent e-mail to the core reflector:
http://lists.isocpp.org/core/2017/09/2930.php

@jensmaurer jensmaurer added the cwg Issue must be reviewed by CWG. label Sep 15, 2017
@jensmaurer jensmaurer self-assigned this Sep 15, 2017
@jensmaurer jensmaurer added this to the C++20 milestone Sep 15, 2017
@timsong-cpp
Copy link
Contributor Author

It looks like it would be correct to revert to the previous example, since function argument evaluations are now indeterminately sequenced, which is a form of unspecified behavior ("either A is sequenced before B or B is sequenced before A, but it is unspecified which") :)

@jensmaurer jensmaurer mentioned this issue Feb 17, 2018
Merged
@jensmaurer jensmaurer changed the title Wrong example of unspecified behavior in [intro.execution]/3 Wrong example of unspecified behavior in [intro.abstract]/3 Feb 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
cwg Issue must be reviewed by CWG.
Projects
None yet
Milestone
C++20 IS
Development

No branches or pull requests
2 participants
@timsong-cpp @jensmaurer