From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6896 invoked by alias); 22 May 2008 19:05:47 -0000 Received: (qmail 6884 invoked by uid 22791); 22 May 2008 19:05:47 -0000 X-Spam-Check-By: sourceware.org Received: from ishtar.tlinx.org (HELO ishtar.tlinx.org) (64.81.245.74) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 22 May 2008 19:05:27 +0000 Received: from [192.168.3.11] (Athena [192.168.3.11]) by ishtar.tlinx.org (8.14.1/8.12.10/SuSE Linux 0.7) with ESMTP id m4MJ5PYL024151 for ; Thu, 22 May 2008 12:05:26 -0700 Message-ID: <4835C3F5.8050706@tlinx.org> Date: Thu, 22 May 2008 19:14:00 -0000 From: Linda Walsh User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: wstring support in GCC 4.1.2 (OS independent) References: <17275355.post@talk.nabble.com> <17290164.post@talk.nabble.com> <4830F08D.6040505@cygwin.com> <17345729.post@talk.nabble.com> <4833813A.7B6F7FAF@dessent.net> In-Reply-To: <4833813A.7B6F7FAF@dessent.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2008-05/txt/msg00438.txt.bz2 Brian Dessent wrote: > jadooo wrote: > >> Please let me know if I am doing anything wrong. > > Yes, you are misunderstanding the nature of the problem. > > In order to support the wstring class, gcc relies on the platform's libc > supporting wide character C99 functions. --- Even though the "kernel" (cygwin 1.5) doesn't support unicode shouldn't it be possible -- and desirable for gcc to support the 'wstring' datatype? It does seem 'wstring' is supported on standard linux, but internally, the kernel doesn't support double-wide characters anymore than cygwin. 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? 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. -- 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/