X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 5 Feb 2009 12:29:58 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Standard conformance for wide characters Message-ID: <20090205112958.GR16129@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Feb 5 12:16, Fr?d?ric Bron wrote: > I am forwarding this email from the boost mailing list. > I basically says that the next version of the boost filesystem library > (a well known library for C++ programming at www.boost.org) will not > compile on cygwin because of the lack of wide character support. > What can be done to make gcc/g++ standard conformant on this point so > that C++ programmers can continue to use cygwin? Cygwin is using the wide char functions provided by newlib. Newlib (http://sources.redhat.com/newlib/) is still lacking a couple of wide char functions so far, namely: fwprintf fwscanf swprintf swscanf vfwprintf vswprintf vwprintf wprintf wscanf wcstod wcstof wcstold wcsftime wcstok wcstok has been contributed but isn't checked in so far. As for all the other functions, contributions to newlib are always welcome on the newlib mailing list. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/