X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
X-Authority-Analysis: v=1.0 c=1 a=OFhHkyISl40A:10 a=i5LJ6xGOLc0A:10  a=xe8BsctaAAAA:8 a=uwz8uI4682B_fEldWPUA:9 a=ip_S8HR2C4FSSxxXerZTP-5p-qQA:4  a=eDFNAWYWrCwA:10 a=rPt6xJ-oxjAA:10
Message-ID: <48362283.2010103@byu.net>
Date: Thu, 22 May 2008 19:48:51 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Thunderbird/2.0.0.14 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: wstring support in GCC 4.1.2 in Cygwin 1.5.25-11
References: <17275355 DOT post AT talk DOT nabble DOT com> <17359564 DOT post AT talk DOT nabble DOT com> <4835C5F9 DOT 7010201 AT tlinx DOT org>
In-Reply-To: <4835C5F9.7010201@tlinx.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Linda Walsh on 5/22/2008 1:14 PM:
|     Linux doesn't support double-wide characters in its
| system calls -- it's all in 'glibc'.
|
|     Cygwin doesn't need to support unicode anymore than
| the linux kernel does.  It's whoever built the gcc/glib
| packages that needs to supply that application-level (not
| system-level) datatype.

Please get your terms straight.  glib is something MUCH different than
glibc.  glib is ported to cygwin, glibc is not.  glib is a graphics
library, glibc is an implementation of libc.  Cygwin uses newlib as its
implementation of libc.  And that's why cygwin doesn't support wstring -
because newlib does not have very complete wide character support.

But you are correct that it is the job of libc, and not the kernel, to
provide application-level code that interprets byte sequences as wide
characters.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkg2IoMACgkQ84KuGfSFAYDXtQCeI20yMSPSKhvW2wdRhiZfSm3V
usIAoKJ/i0GgKQJeVfPJSt92y+fe8VAB
=hwpH
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/