Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org,  Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com,  alexeyf@opera.com
Subject: Re: Default target wide character set
Date: Thu, 17 Sep 2009 10:25:00 -0000	[thread overview]
Message-ID: <200909171125.11172.pedro@codesourcery.com> (raw)
In-Reply-To: <83ws3ywrl3.fsf@gnu.org>

On Wednesday 16 September 2009 21:40:56, Eli Zaretskii wrote:
> > From: Pedro Alves <pedro@codesourcery.com>
> > Date: Wed, 16 Sep 2009 20:11:18 +0100
> > Cc: "Alexey Feldgendler" <alexeyf@opera.com>
> > 
> > Something like that would also be useful for Windows targets, and would
> > address PR9996:
> > 
> >  http://sourceware.org/bugzilla/show_bug.cgi?id=9996
> 
> Are you sure this PR still holds with the newer Cygwin 1.7? does
> Cygwin still use 2-byte wchar_t?

I'm not 100% sure, but I'm 99.9(9)% sure, but only because I
didn't take the trouble to confirm it myself.  Why wouldn't it?  Given
that 2-byte WCHAR is what Windows NT uses internally to store and handle
strings, and hence what is passed back and forth between Cygwin and
the NT and Win32 APIs Cygwin uses to do its business, switching away
from 2-byte wchar_t on Cygwin doesn't sound like a bad idea to me.

-- 
Pedro Alves


  parent reply	other threads:[~2009-09-17 10:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 14:12 Alexey Feldgendler
2009-09-16 18:56 ` Tom Tromey
2009-09-16 19:11   ` Pedro Alves
2009-09-16 20:41     ` Eli Zaretskii
2009-09-16 20:46       ` Tom Tromey
2009-09-17 10:25       ` Pedro Alves [this message]
2009-09-16 20:40   ` Eli Zaretskii
2009-09-16 20:46     ` Tom Tromey
2009-09-16 20:54       ` Eli Zaretskii
2009-09-17  8:50   ` Alexey Feldgendler
2009-09-18 20:42     ` Tom Tromey

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=200909171125.11172.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=alexeyf@opera.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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