Re: workaround against broken duplocale

2017-08-15 Thread Joerg Sonnenberger
On Tue, Aug 15, 2017 at 11:39:38PM +0200, Bruno Haible wrote: > Hi Jörg, > > Joerg Sonnenberger wrote: > > uselocale() is fundamentally broken from a design perspective. It can't > > be implemented without breaking ABIs. > > Well, glibc did not break ABIs when it introduced uselocale() in 2002.

Re: workaround against broken duplocale

2017-08-15 Thread Bruno Haible
Hi Jörg, Joerg Sonnenberger wrote: > uselocale() is fundamentally broken from a design perspective. It can't > be implemented without breaking ABIs. Well, glibc did not break ABIs when it introduced uselocale() in 2002. If you have not exposed too many internals of the locale set by setlocale(),

Re: workaround against broken duplocale

2017-08-15 Thread Joerg Sonnenberger
On Tue, Aug 15, 2017 at 09:28:26PM +0200, Bruno Haible wrote: > Which is pretty senseless, since it forces programs to use functions that take > an explicit locale argument (fprintf_l, strfmon_l, and similar). The point > of standardizing duplocale(), newlocale(), uselocale() was to *eliminate* >

workaround against broken duplocale

2017-08-15 Thread Bruno Haible
Hi, Running a gnulib testdir on NetBSD, I'm seeing a link error for test-duplocale. This is due to the fact that the NetBSD people implemented duplocale() without uselocale(). https://mail-index.netbsd.org/tech-userlevel/2013/04/23/msg007714.html Which is pretty senseless, since it forces