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.

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

[dcl.type.cv]/6 "program behavior" vs "behavior" #599

Merged
merged 1 commit into from Mar 7, 2016
Merged

[dcl.type.cv]/6 "program behavior" vs "behavior" #599

merged 1 commit into from Mar 7, 2016

Conversation

Arcoth
Copy link
Contributor

@Arcoth Arcoth commented Jan 9, 2016

[dcl.type.cv]/6 reads

If an attempt is made to refer to an object defined with a volatile-qualified type through the use of a glvalue with a non-volatile-qualified type, the program behavior is undefined.

This is probably meant to use the idiomatic phrase "the behavior is undefined".

[dcl.type.cv]/6 reads

> If an attempt is made to refer to an object defined with a volatile-qualified type through the use of a glvalue with
a non-volatile-qualified type, the program behavior is undefined.

This is probably meant to use the much more idiomatic phrase "the behavior is undefined". A distinction between well-definedness of the program's and the implementation's behavior would presumably be inappropriate, anyway.
zygoloid added a commit that referenced this pull request Mar 7, 2016
[dcl.type.cv] "program behavior is undefined" -> "behavior is undefined"
@zygoloid zygoloid merged commit 14062f4 into cplusplus:master Mar 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants