From 1ae4bc42808111d6b3f50c063de102f162051986 Mon Sep 17 00:00:00 2001 From: Rich Felker Date: Sun, 28 Jul 2013 03:41:01 -0400 Subject: fix semantically incorrect use of LC_GLOBAL_LOCALE LC_GLOBAL_LOCALE refers to the global locale, controlled by setlocale, not the thread-local locale in effect which these functions should be using. neither LC_GLOBAL_LOCALE nor 0 has an argument to the *_l functions has behavior defined by the standard, but 0 is a more logical choice for requesting the callee to lookup the current locale. in the future I may move the current locale lookup the the caller (the non-_l-suffixed wrapper). at this point, all of the locale logic is dummied out, so no harm was done, but it should at least avoid misleading usage. --- src/locale/langinfo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/locale/langinfo.c') diff --git a/src/locale/langinfo.c b/src/locale/langinfo.c index b4d53744..7bb56eed 100644 --- a/src/locale/langinfo.c +++ b/src/locale/langinfo.c @@ -60,7 +60,7 @@ char *__nl_langinfo_l(nl_item item, locale_t loc) char *__nl_langinfo(nl_item item) { - return __nl_langinfo_l(item, LC_GLOBAL_LOCALE); + return __nl_langinfo_l(item, 0); } weak_alias(__nl_langinfo, nl_langinfo); -- cgit v1.2.1