From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Julian Brown <julian@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH/WIP] C/C++ wchar_t/Unicode printing support
Date: Thu, 15 Jan 2009 21:18:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0901152112030.15655@digraph.polyomino.org.uk> (raw)
In-Reply-To: <m3r634jneg.fsf@fleche.redhat.com>
On Thu, 15 Jan 2009, Tom Tromey wrote:
> * Handles input and output of wide characters and strings, and also
> the new C0X u"" and U"" syntax.
(Of course, now C++0x has and C1x has accepted (not yet in a draft) a lot
of further new string syntax that Jakub has implemented for GCC 4.5.)
If you handle input of the new string syntax, do you also handle the
interesting concatenation issues? "\xab" L"c" is a wide string with two
characters, L'\xab' and L'c' (plus the trailing NUL); you do not interpret
'\xab' as a member of the target narrow character set and convert to the
target wide character set (nor do you interpret it as L"\xabc", with a
single escape sequence), so you can't convert escape sequences to bytes of
a string until after you know whether the final string is narrow or wide
(or some other variant, in C++0x/C1x).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-01-15 21:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 20:24 Julian Brown
2009-01-15 21:02 ` Tom Tromey
2009-01-15 21:18 ` Joseph S. Myers [this message]
2009-01-16 0:01 ` Tom Tromey
2009-01-15 22:16 ` Julian Brown
2009-01-16 0:53 ` Tom Tromey
2009-01-16 9:36 ` Eli Zaretskii
2009-01-16 16:18 ` Tom Tromey
2009-01-16 16:40 ` Eli Zaretskii
2009-01-16 16:57 ` Mark Kettenis
2009-01-30 4:11 ` Tom Tromey
2009-01-30 22:14 ` Joel Brobecker
[not found] ` <m3ocxos6og.fsf@fleche.redhat.com>
2009-02-01 18:23 ` Daniel Jacobowitz
2009-02-01 22:42 ` Tom Tromey
2009-02-01 23:16 ` Daniel Jacobowitz
2009-02-01 23:18 ` Daniel Jacobowitz
2009-02-01 23:26 ` Tom Tromey
2009-02-03 0:41 ` Joel Brobecker
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=Pine.LNX.4.64.0901152112030.15655@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=julian@codesourcery.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