public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nachms+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/55971] New: Preprocessor macros with C++11 raw string literals fail to compile
Date: Mon, 14 Jan 2013 15:23:00 -0000	[thread overview]
Message-ID: <bug-55971-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55971

             Bug #: 55971
           Summary: Preprocessor macros with C++11 raw string literals
                    fail to compile
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: nachms+gcc@gmail.com


It does not seem possible to create a macro which contains a C++ raw string
literal, when it should be.

Example:
-----------------
#include <iostream>

#define CREATE_CLIENTS R"(CREATE TABLE "clients"(
  "clientId" INTEGER PRIMARY KEY AUTOINCREMENT,
  "clientName" VARCHAR(64) UNIQUE
))"

int main()
{
  std::cout << CREATE_CLIENTS << std::endl;
  return 0;
}
-----------------
g++ -W -Wall -o test test.cpp -std=c++11
test.cpp:3:24: error: unterminated raw string
test.cpp:6:3: warning: missing terminating " character [enabled by default]
test.cpp:6:1: error: missing terminating " character
test.cpp:10:3: error: stray ‘R’ in program
test.cpp:4:3: error: expected unqualified-id before string constant

On the other hand, clang seems to be able to handle it:
clang++ -W -Wall -o test test.cpp -std=c++11
./test
CREATE TABLE "clients"(
  "clientId" INTEGER PRIMARY KEY AUTOINCREMENT,
  "clientName" VARCHAR(64) UNIQUE
)


             reply	other threads:[~2013-01-14 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 15:23 nachms+gcc at gmail dot com [this message]
2013-01-14 15:39 ` [Bug preprocessor/55971] " redi at gcc dot gnu.org
2013-01-14 15:48 ` nachms+gcc at gmail dot com
2013-01-14 15:56 ` redi at gcc dot gnu.org
2013-01-14 16:36 ` jakub at gcc dot gnu.org
2013-01-14 16:44 ` redi at gcc dot gnu.org
2013-01-14 17:34 ` jakub at gcc dot gnu.org
2022-06-17 22:23 ` lhyatt at gcc dot gnu.org
2022-11-05 14:31 ` cvs-commit at gcc dot gnu.org
2022-11-05 14:33 ` lhyatt at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-55971-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).