This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH/WIP] C/C++ wchar_t/Unicode printing support
- From: Tom Tromey <tromey at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Julian Brown <julian at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Fri, 16 Jan 2009 09:15:39 -0700
- Subject: Re: [PATCH/WIP] C/C++ wchar_t/Unicode printing support
- References: <20090115202411.5f154657@rex.config> <u3afjwq2c.fsf@gnu.org>
- Reply-to: tromey at redhat dot com
>>>>> "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