-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ludovic Courtès on 11/23/2009 4:01 PM: >> const char *base_name = nl_langinfo (_NL_LOCALE_NAME (LC_CTYPE)); > > This is not thread-safe but I guess there’s no other choice.
As is the case with a number of gnulib modules. But I have been trying to document that in the various files; for example, note how doc/posix-functions/openat.texi mentions that the replacement is not thread-safe. > On a related note, nl_langinfo_l(3) is broken in current glibc: > > http://sourceware.org/bugzilla/show_bug.cgi?id=11009 For once, I'm tending to agree with Uli - the use of the global locale is important for duplocale to create a one-off variant locale, but when it comes to all the *_l interfaces, if you want the global locale, then use what got returned by duplocale, rather than teaching all the _l interfaces to special case the placeholder constant for the global locale. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksLUZsACgkQ84KuGfSFAYBsnACaA8Z2znPI2z8RiYn70mnIMrtG D1gAoJwIbDyRcYPJzL1mVpUKPZvTY5in =Np1G -----END PGP SIGNATURE-----
