X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <48363374.58ECFB68@dessent.net>
Date: Thu, 22 May 2008 20:01:08 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: wstring support in GCC 4.1.2 (OS independent)
References: <17275355 DOT post AT talk DOT nabble DOT com> <17290164 DOT post AT talk DOT nabble DOT com> <4830F08D DOT 6040505 AT cygwin DOT com> <17345729 DOT post AT talk DOT nabble DOT com> <4833813A DOT 7B6F7FAF AT dessent DOT net> <4835C3F5 DOT 8050706 AT tlinx DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

Linda Walsh wrote:

> So maybe the problem is
> not that cygwin doesn't support unicode, but that the gcc
> libs & compile utils don't support the standard linux
> equivalents?

I can't parse this.

>         Whether or not cygwin (or the linux kernel) supports
> "wchar" is not entirely relevant to what the application libraries
> on top of the kernel support -- at least going by the example
> on an x86_64 linux.  It's still the case that the 64-bit
> linux kernel doesn't support wchars any more than cygwin, yet
> the compiler suite does.

Comparing Cygwin to the linux kernel is nonsense.  They serve totally
different purposes -- Cygwin is a user-mode library.  If you want to
make a comparison, compare Cygwin to glibc as they are both libcs.

And again, the compiler suite cannot implement wstring without
underlying libc wide character IO support which does not exist in newlib
and therefore does not exist in Cygwin.  Remember that gcc is divorced
from the target libc because a libc is way too OS-dependent.  gcc relies
on the platform to implement its own libc, and everything gcc implements
builds on top of an existing libc.  If the libc doesn't have the
necessary support there's nothing that libstdc++ can do about it but
disable wstring.

Brian

--
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/