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
[compatibility] Add compatibility notices for pp-number #713
Conversation
|
||
\begin{codeblock} | ||
#define F(a) b ## a | ||
int b0p = F(0p0+0); // ill-formed; equivalent to ``\tcode{int b0p = b0p + 0;}\!'' in C++ 2003 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is F(0p+0)
meant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timsong-cpp: Yes :-)
We generally only list differences against other languages in one subclause of Annex C. |
@zygoloid: So where should this go: break from C++14, or from C++03? |
@zygoloid: Now there's only a single compatibility note against C++14, with the both examples. |
Valid \CppXI code may fail to compile or produce different results in | ||
this International Standard. Specifically, character sequences like \tcode{0p+0} | ||
and \tcode{0e1_p+0} are three separate tokens each in \CppXIV, but one single token | ||
in this International Standard. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Valid \CppXI code"...."in \CppXIV"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well spotted, thanks! Fixed.
d75230e
to
ba7598b
Compare
Updated, thanks @timsong-cpp. New screenshot: @zygoloid: PTAL |
Addresses #680.