X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <4833813A.7B6F7FAF@dessent.net> Date: Tue, 20 May 2008 18:56:10 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: jadooo CC: 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> <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> 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: List-Subscribe: List-Archive: List-Post: List-Help: , 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: > 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. newlib does not have the necessary support[1] so until that work is contributed, the wstring class cannot be enabled in libstdc++. And even then, you'd have to rebuild libstdc++ which means rebuilding all of gcc. Cygwin 1.7 currently contains support for unicode characters in filenames, but this is a far cry from general wide character string support (e.g. wprintf) so simply upgrading to 1.7 will not do anything. Larry's suggestion that this will start working in 1.7 is premature, unless somebody contributes the necessary newlib improvements before 1.7 is released. Brian [1] For a list of the missing features see http://cygwin.com/ml/cygwin-developers/2008-04/msg00094.html -- 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/