-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
handle C++ raw string in a single token #7
Comments
It looks like gcc handle the raw string in the preprocessor, see here as a reference: 55971 – Preprocessor macros with C++11 raw string literals fail to compile |
Jup. You're right. C++ raw strings (like The only thing that comes close is If it's any consolation to you, I've also been planning to add So: will be implemented eventually (but no promises as to when). But: |
Hi, thanks for the detailed explanation. My interest about learning some C-preprocessor code is to improve the embedded parser(To fetch some Symbols in the source files) inside the Code::Blocks. universal-ctags/ctags: A maintained ctags implementation danmar/cppcheck: static analysis of C/C++ code with its preprocessor danmar/simplecpp: C++ preprocessor A preprocessor is a very low level tool base to supply a token stream to the high level parsers. |
Hi, from the page: https://en.cppreference.com/w/cpp/language/string_literal
There are many kinds of C++ raw strings, while I see the lexer/preprocessor should handle them as a single token. While currently they are handled as separate tokens, for example:
In the above cases, the "U" will be parsed as a single Token, and with the same Token id.
Thanks.
The text was updated successfully, but these errors were encountered: