delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
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 |
To: | cygwin AT cygwin DOT com |
From: | "Beman Dawes" <bdawes AT acm DOT org> |
Subject: | Wide character support for GCC? |
Date: | Thu, 26 May 2005 21:57:54 -0400 |
Lines: | 9 |
Message-ID: | <d75un4$hfb$1@sea.gmane.org> |
X-RFC2646: | Format=Flowed; Original |
X-IsSubscribed: | yes |
What's the story on wide character support for GCC? Are wchar_t, std::wstring, etc., still not supported by cygwin? If not, what would it take to get wide character support working? Is there a lot of work involved? Is it something an outside developer could contribute? --Beman Dawes -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |