public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11009] `nl_langinfo_l (item, LC_GLOBAL_LOCALE)' crashes
Date: Tue, 24 Nov 2009 01:12:00 -0000 [thread overview]
Message-ID: <20091124011231.6085.qmail@sourceware.org> (raw)
In-Reply-To: <20091123224038.11009.ludo@gnu.org>
------- 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.
next prev parent reply other threads:[~2009-11-24 1:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 22:40 [Bug libc/11009] New: " ludo at gnu dot org
2009-11-23 22:42 ` [Bug libc/11009] " ludo at gnu dot org
2009-11-23 22:47 ` drepper at redhat dot com
2009-11-23 23:01 ` jakub at redhat dot com
2009-11-23 23:44 ` ludo at gnu dot org
2009-11-23 23:48 ` drepper at redhat dot com
2009-11-24 1:12 ` bruno at clisp dot org [this message]
[not found] <bug-11009-131@http.sourceware.org/bugzilla/>
2014-06-30 20:38 ` fweimer at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091124011231.6085.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).