From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6103 invoked by alias); 24 Nov 2009 01:12:41 -0000 Received: (qmail 6086 invoked by uid 48); 24 Nov 2009 01:12:31 -0000 Date: Tue, 24 Nov 2009 01:12:00 -0000 Message-ID: <20091124011231.6085.qmail@sourceware.org> From: "bruno at clisp dot org" To: glibc-bugs@sources.redhat.com In-Reply-To: <20091123224038.11009.ludo@gnu.org> References: <20091123224038.11009.ludo@gnu.org> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/11009] `nl_langinfo_l (item, LC_GLOBAL_LOCALE)' crashes X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00155.txt.bz2 ------- Additional Comments From bruno at clisp dot org 2009-11-24 01:12 ------- (In reply to comment #3) > If you want to query the global locale, why don't you just use > nl_langinfo instead of nl_langinfo_l? Note that the proposed nl_langinfo_l (item, LC_GLOBAL_LOCALE) is not equivalent to nl_langinfo (item) but rather to ({ locale_t old_thread_locale = uselocale (LC_GLOBAL_LOCALE); const char *value = nl_langinfo (item); uselocale (old_thread_locale); value; }) or to ({ locale_t global_locale = duplocale (LC_GLOBAL_LOCALE); const char *value = nl_langinfo_l (item, global_locale); freelocale (global_locale); value; }) But I agree with your evaluation that it is not essential to support LC_GLOBAL_LOCALE arguments here (unlike in duplocale, see bug10969). -- http://sourceware.org/bugzilla/show_bug.cgi?id=11009 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.