-
Notifications
You must be signed in to change notification settings - Fork 769
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
[class] Incorrect cross-references #4004
Comments
Regarding [class.derived], [expr.eq] p3.3 actually requires (indirectly) that comparisons of pointers to different complete objects of non-zero size yield the result "unequal", so this is in fact relevant. However, [intro.object] is probably a better reference. I agree the reference to [basic.stc] is bogus. Regarding [class.access.spec], [expr.rel] p4.2 indeed discusses order of allocation, because pointer comparisons (but nothing else) induce constraints on the allocation order. |
Thanks for commenting on this. Careful reading of [expr.eq] proved I jumped to somewhat wrong conclusions. However, it is still better to add some informal note regarding this directly under [expr.eq] subclause. [intro.object] addresses the issue directly, so, probably, the best solution is just to use it in place of [expr.eq]. In the passage from [class.access.spec] order of allocation is a bit confusing. [class.mem]/19 is about the same but its wording is much clearer. I missed that in essence subsequent allocations give higher addresses; without that the passage is pointless. Also, I'll edit the title of the issue to be less radical. |
[class.mem] p19 is a note; everything there should be expressed normatively elsewhere. |
Some examples:
draft/source/classes.tex
Lines 3588 to 3597 in fc974c3
draft/source/classes.tex
Lines 4714 to 4717 in fc974c3
The list is incomplete. Most broken references (if not all) point to either [basic] or [expr]. Other clauses seem more accurate.
The text was updated successfully, but these errors were encountered: