From: Jakub Jelinek <jakub@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Tom Tromey <tromey@redhat.com>, Jason Merrill <jason@redhat.com>,
gcc-patches@gcc.gnu.org,
Kris Van Hees <kris.van.hees@oracle.com>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: [PATCH] Support for C++0x and C1x u8 string literals and raw string literals
Date: Fri, 12 Sep 2008 19:40:00 -0000 [thread overview]
Message-ID: <20080912191951.GC9666@hs20-bc2-1.build.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0809121541540.17535@digraph.polyomino.org.uk>
On Fri, Sep 12, 2008 at 03:56:38PM +0000, Joseph S. Myers wrote:
> > be really pedantic and accept only basic source charset character except
> > the listed 7, rather than say all characters except the listed 7
> > plus maybe disallowing '\0', as this is a new feature I think being
>
> > pedantic doesn't hurt. In one of the raw string papers floating
> > around there was an example using R"@[...]@" which is not pedantically
> > valid, as @ is not basic source charset character. u8 string
>
> But that example is conditionally valid in C++ only, although not in C,
> because in phase 1 @ will have been converted to a UCN (part of the
> existing C++98 semantics we don't implement). The validity is only
> conditional because there is no requirement to use the same UCN for each
> instance of @.
UCNs aren't valid in d-char-sequence though, only in normal strings and within
r-char-sequence.
raw-string:
" d-char-sequenceopt [ r-char-sequenceopt ] d-char-sequenceopt "
r-char-sequence:
r-char
r-char-sequence r-char
r-char:
any member of the source character set, except
(1), a backslash \followed by a u or U, or
(2), a right square bracket ] followed by the initial d-char-sequence
(which may be empty) followed by a double quote ".
universal-character-name
d-char-sequence:
d-char
d-char-sequence d-char
d-char:
any member of the basic source character set except:
space, the left square bracket [, the right square bracket ],
and the control characters representing horizontal tab,
vertical tab, form feed, and newline.
Jakub
next prev parent reply other threads:[~2008-09-12 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 14:22 Jakub Jelinek
2008-09-12 16:52 ` Joseph S. Myers
2008-09-12 19:40 ` Jakub Jelinek [this message]
2008-09-12 20:16 ` Joseph S. Myers
2008-09-12 21:00 ` Jakub Jelinek
2008-09-12 21:04 ` Joseph S. Myers
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=20080912191951.GC9666@hs20-bc2-1.build.redhat.com \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=kris.van.hees@oracle.com \
--cc=tromey@redhat.com \
/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).