From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Julian Brown <julian@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH/WIP] C/C++ wchar_t/Unicode printing support
Date: Fri, 16 Jan 2009 16:18:00 -0000 [thread overview]
Message-ID: <m3d4eni5w4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <u3afjwq2c.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 16 Jan 2009 11\:36\:11 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> + #ifndef GDB_DEFAULT_TARGET_WIDE_CHARSET
>> + #define GDB_DEFAULT_TARGET_WIDE_CHARSET "UTF-32"
>> + #endif
>> +
>> + #ifndef GDB_INTERNAL_CODESET
>> + #define GDB_INTERNAL_CODESET "UCS-4LE"
>> + #endif
Eli> Why are these the defaults? because of what GNU/Linux (i.e. glibc)
Eli> does, or for some other reason? If the former, shouldn't this be
Eli> autoconfigured?
I don't think there is a way to auto-configure the target wide
charset. Perhaps we could have a new target method to discover it,
when that is possible. Even with that change, though, we would still
need a default. UCS-4 was also the choice I made for this in my
patch, due to glibc.
For the internal codeset ... this is just a choice in this patch, for
target_char_to_internal. There's no reason to add configury for this,
as it is not host-dependent.
Tom
next prev parent reply other threads:[~2009-01-16 16: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
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 [this message]
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=m3d4eni5w4.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--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