On Fri, May 23, 2008 at 11:40:35AM -0700, Linda Walsh wrote: > Eric Blake wrote: >> -----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. > >Where did 'newlib' come from? I "thought", that newlib had originally >been designed as a 'bootstrapping' library in order to get some minimal >and widely used set of gnu-library functions up and running so other >gnu utils could also get "up & running".
Either check out the newlib web site at http://sourceware.org/newlib or ask about newlib in the newlib mailing list. cgf -- 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/
