public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/22042] stringification BUG
Date: Sat, 09 Jul 2005 18:51:00 -0000	[thread overview]
Message-ID: <20050709183246.23414.qmail@sourceware.org> (raw)
In-Reply-To: <20050613052744.22042.s__nakayama@infoseek.jp>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-09 18:32 -------
The relevant part of the standard (C99: 6.10.3.2P2)
Otherwise, the original spelling of each preprocessing token in the argument is retained in the 
character string literal, except for special handling for producing the spelling of string literals and 
character constants: a\character is inserted before each" and \character of a character constant or 
string literal (including the delimiting " characters), except that it is implementation-defined whether 
a\character is inserted before the\character beginning a universal character name. If the replacement 
that results is not a valid character string literal, the behavior is undefined. The character string literal 
corresponding to an empty argument is ""

-- 


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


  parent reply	other threads:[~2005-07-09 18:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13  5:27 [Bug preprocessor/22042] New: " s__nakayama at infoseek dot jp
2005-06-13 12:36 ` [Bug preprocessor/22042] " pinskia at gcc dot gnu dot org
2005-06-14  7:21 ` s__nakayama at infoseek dot jp
2005-06-19 16:27 ` s__nakayama at infoseek dot jp
2005-06-23 15:35 ` s__nakayama at infoseek dot jp
2005-07-09 16:34 ` pinskia at gcc dot gnu dot org
2005-07-09 18:32 ` s__nakayama at infoseek dot jp
2005-07-09 18:51 ` pinskia at gcc dot gnu dot org [this message]
2005-07-13 13:13 ` [Bug preprocessor/22042] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-07-22 21:18 ` pinskia at gcc dot gnu dot org
2005-09-27 16:13 ` mmitchel at gcc dot gnu dot 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=20050709183246.23414.qmail@sourceware.org \
    --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).