Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Thu, 29 Aug 2002 10:34:25 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com, newlib AT sources DOT redhat DOT com Subject: Re: perl giving setlocale failures with recent cygwin's, Egor please comment? Message-ID: <20020829143425.GB26609@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com, newlib AT sources DOT redhat DOT com References: <20020829030930 DOT GA2779 AT redhat DOT com> <6880518559 DOT 20020829125652 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Thu, Aug 29, 2002 at 10:58:47PM +0900, Kazuhiro Fujieda wrote: >>>> On Thu, 29 Aug 2002 12:56:52 +0400 >>>> egor duda said: > >> Yes, it's definitely so. Previously, setlocale (LC_CTYPE, "") was >> returning "C", while now, in MB_CAPABLE configuration, it returns NULL. >> >> I'm not sure whether it's better to fix it in newlib or in perl, though. > >setlocale(category, "") commonly returns "C" when any relevant >environment variables aren't set. The MB_CAPABLE version of >setlocale should be fixed. Is it not doing that? AFAICT, that's how it works. cgf