X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <4835C5F9.7010201@tlinx.org>
Date: Thu, 22 May 2008 12:14:01 -0700
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: jadooo <vnair AT linx DOT co DOT uk>, cygwin AT cygwin DOT com
Subject: Re: wstring support in GCC 4.1.2 in Cygwin 1.5.25-11
References: <17275355 DOT post AT talk DOT nabble DOT com> <17359564 DOT post AT talk DOT nabble DOT com>
In-Reply-To: <17359564.post@talk.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

jadooo wrote:
> Thanks a lot for the valuable information.
> 
> I am trying to port my application developed in linux to windows, now as
> it is quiet clear that I could not use cygwin, due to lack of Unicode
> support,
> is there any other alternative to try out my porting activity.
---
	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.

	In the same way, gcc/glib supports 64-bit data types
on 32-bit machines and the glib file I/O transparently supports
64-bit file offsets even on 32-bit machines.

	But, AFAIK, glib doesn't support calling the standard
*nix file-io calls with 'wchar' comprised wstrings.


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