X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.0 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Date: Thu, 5 Feb 2009 12:16:07 +0100
Message-ID: <a9a39a210902050316o51cc83eeu1fbe471edadf926@mail.gmail.com>
Subject: Standard conformance for wide characters
From: =?UTF-8?B?RnLDqWTDqXJpYyBCcm9u?= <frederic DOT bron AT m4x DOT org>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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

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?

F. Bron

boost-bounces AT lists DOT boost DOT org a =C3=A9crit sur 13/01/2009 15:16:02 :
> I've decided not to attempt support for Cygwin in the next version of
> Boost.Filesystem.
>
> Cygwin's lack of library support for wchar_t is the problem . For the
> current Boost.Filesystem version (v2), the necessary workarounds are so
> pervasive that the implementation code is much harder to read and
> maintain. Witness the number of bug reports that are Cygwin specific.
> For v3, currently under development, trying to support Cygwin would be
> even harder, and would cause a serious delay in development. Plus I'm
> tired of waiting for the cygwin folks to come into full C++ conformance.
>
> IIUC, the reason Cygwin doesn't provide C++ standard library support for
> wchar_t is that the underlying C library is missing the C wchar_t
> functions. Perhaps Boosters who care about Cygwin could spearhead an
> effort to add the missing C support? The needed functionality isn't all
> that complex; the main problem might be just learning enough about how
> Cygwin/GCC is configured and built to be able to add a fairy small
> number of C functions.
>
> Thoughts?
>
> --Beman

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