-
Notifications
You must be signed in to change notification settings - Fork 97
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
Missing referenced type named "C" in section 2.2, "POD Data Types" #190
Comments
My guess is that "C type" refers to this C-style type definition presented further below:
|
Thanks, Jens. That seems likely. There would still be a gap for pointers to data members though. |
A pointer to data member is explained to be an offset stored in a |
Indeed, but the "A member pointer type is treated exactly as if it were the C type described below" wording doesn't differentiate between data members and member functions. It seems that "the C type described below" must be intended to refer to different parts of the prose; for pointers to data members, the C type is In 2.3.1 Data Member Pointers:
In 2.3.2 Member Function Pointers:
This would make sense as the intent. I think the wording can still be improved though. |
That is the intent, yes. I'm open to suggestions about how to improve the wording. |
Maybe just remove the "C":
|
That helps, but there are two types to choose from (for data members vs member functions). Perhaps:
|
Section 2.2 "POD Data Types" states:
The "described below" link references section 2.3, "Member Pointers". That section does not contain any prose but it does have two subsections, section 2.3.1, "Data Member Pointers" and section 2.3.2, Member Function Pointers", neither of which defines a type named "C".
Section 2.4, "Non-POD Class Types" uses the name "C" as a generic identifier for a class type. If this is the type intended by the "C type" reference, then the "described below" link should be updated to reference this section. I don't see an obvious way in which the "C" type described there fits with the "member pointer type is treated exactly as if it were the C type" wording though, so it seems that some other elucidation is still required.
The text was updated successfully, but these errors were encountered: