This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: wstring support in GCC 4.1.2 in Cygwin 1.5.25-11
-----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@byu.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/