[expr.rel] Clarify confusing wording CWG2749#6173
Closed
lprv wants to merge 1 commit into
Closed
Conversation
Member
|
What's wrong with the existing text? A "pointer to void" is not a pointer to object, because void is not an object type. |
Contributor
Author
|
The text is talking about values, and |
Contributor
|
@jensmaurer Any further thoughts? This seems like a corish detail I'd defer to you on. |
Member
|
I think this is good, but CWG should have a look because it's a bit of a delicate wording here. |
Contributor
|
@jensmaurer Is there a core issue for this? |
Member
|
CWG 2023-06-14: Needs research on C behavior for "pointer to void". |
Contributor
|
It appears that this is now CWG2749? |
Member
|
Yes. |
Contributor
|
Already handled by CWG issue. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
'Pointer to an object' is one of the pointer value categories defined in [basic.compound], but according to CWG2526 the intended reading here is that
void*values are excluded from the ordering.