You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The # operator for stringizing tokens behaves non-standardly in at least the following respects:
It does not insert spaces corresponding to white space between its argument tokens.
When applied to a string literal, it should generate a string corresponding to the original representation of the string in the source file, including " delimiters and escape sequences using \ (and those characters are at least conceptually escaped with \ to permit this). Currently, it gives a string literal equivalent to the one passed to it, but does not include the delimiters and escape sequences from its actual representation in the source file.
The text was updated successfully, but these errors were encountered:
Commit 76eb476 addresses several issues related to the # operator, but still leaves some others. These include that escape sequences in strings are not handled properly and that comments between tokens can cause problems.
Here is a program that illustrates some remaining issues:
The
#
operator for stringizing tokens behaves non-standardly in at least the following respects:"
delimiters and escape sequences using\
(and those characters are at least conceptually escaped with\
to permit this). Currently, it gives a string literal equivalent to the one passed to it, but does not include the delimiters and escape sequences from its actual representation in the source file.The text was updated successfully, but these errors were encountered: