From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Julian Brown <julian@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH/WIP] C/C++ wchar_t/Unicode printing support
Date: Sun, 01 Feb 2009 23:26:00 -0000 [thread overview]
Message-ID: <m3d4e1rbak.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090201231604.GA24974@caradoc.them.org> (Daniel Jacobowitz's message of "Sun\, 1 Feb 2009 18\:16\:04 -0500")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> As far as portability goes, we may have to experiment. But I can tell
Daniel> you flat out that swprintf is going to be a problem; it's a C99
Daniel> library function and most hosts don't have C99 library extensions.
Thanks. It is no trouble to avoid swprintf, I'll make this change.
Tom> I think "set charset" already does this. It doesn't handle the target
Tom> wide charset, but that seems ok in the degraded functionality mode.
Daniel> Right. Except that if the wide charset remains unchanged, validate
Daniel> will report an error since it can't convert to it...
Oh, duh. Yeah.
Tom
next prev parent reply other threads:[~2009-02-01 23:26 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
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 [this message]
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=m3d4e1rbak.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=julian@codesourcery.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