This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: wstring support in GCC 4.1.2 in Cygwin 1.5.25-11

Eric Blake wrote:
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".

	Wasn't it planned to bring in the full glibc at one point? --
and sorry for my terminology -- I'm often a lazy typist -- my typing
isn't what it used to be -- due to nerve impingements...I usually do
ok, but it depends on how much I've pushed, how tired or taxed I am...
I knew the correct name of glibc -- as put in quotes in the first
sentence...was latter on in 'backrefs', I got more lazy...sigh

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]