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
What should the standard say for changes listed in Annex C that are backported by implementations? #6247
Comments
No, they should not be removed. They describe differences between C++ standards, and so should be documented in the standard. Those differences don't disappear just because implementations backport them. The behaviour of implementations should be documented by implementations, not in the standard. |
I'd expect a brief note that describes the reality. Otherwise readers could be misled. |
Users are not reading the annexes of the standard |
These are informational notes about changes between revisions of ISO standards. If you want to know about real world implementation status, look elsewhere. |
Agreed with @jwakely ; the standard is not the manual for your implementation. I think the phrasing in the Annex is clear that it discusses differences between releases of the standard. |
Should we say which changes in Annex C are officially defect reports? |
There are no defect reports for C++, since we release a new standard every three years (that, officially, is unrelated to any previous standard). We would have Defect Reports if we would publish a TC (Techincal Corrigendum). |
Some changes are listed in Annex C [diff] as differences between versions of C++, but implementations choose the new behavior even in old standard modes. Examples are:
Should there be a note saying that implementations sometimes apply these changes in old standard modes?
Should these changes be removed from Annex C?
The text was updated successfully, but these errors were encountered: