Can we get rid of our `kw_L__FUNCTION__` hack with this change?
No, I don't think we can. My solution fixes only lexer, but when we building
L__FUNCTION__ we're building an expression.
Best regards,
Alexey Bataev
=============
Software Engineer
Intel Compiler Team
12.12.2014 7:39, David Majnemer пишет:
Can we get rid of our `kw_L__FUNCTION__` hack with this change?
================
Comment at: lib/Lex/TokenLexer.cpp:524
@@ -515,2 +523,3 @@
PasteOpLoc = Tokens[CurToken].getLocation();
- ++CurToken;
+ if (Tokens[CurToken].is(tok::hashhash))
+ ++CurToken;
----------------
What's the rationale behind this change?
http://reviews.llvm.org/D6604
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
