From d67aea28f6cb180291f95690ece485740f3fe859 Mon Sep 17 00:00:00 2001 From: Richard Smith Date: Tue, 6 Mar 2012 03:21:47 +0000 Subject: User-defined literals: reject string and character UDLs in all places where the grammar requires a string-literal and not a user-defined-string-literal. The two constructs are still represented by the same TokenKind, in order to prevent a combinatorial explosion of different kinds of token. A flag on Token tracks whether a ud-suffix is present, in order to prevent clients from needing to look at the token's spelling. llvm-svn: 152098 --- clang/lib/Lex/ModuleMap.cpp | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'clang/lib/Lex/ModuleMap.cpp') diff --git a/clang/lib/Lex/ModuleMap.cpp b/clang/lib/Lex/ModuleMap.cpp index 28043d1..e6851af 100644 --- a/clang/lib/Lex/ModuleMap.cpp +++ b/clang/lib/Lex/ModuleMap.cpp @@ -617,6 +617,12 @@ retry: break; case tok::string_literal: { + if (LToken.hasUDSuffix()) { + Diags.Report(LToken.getLocation(), diag::err_invalid_string_udl); + HadError = true; + goto retry; + } + // Parse the string literal. LangOptions LangOpts; StringLiteralParser StringLiteral(<oken, 1, SourceMgr, LangOpts, *Target); -- cgit v1.1