Bruno Haible wrote:
> On MacOS X 10.5, which has newlocale() and uselocale(), c-strtod is still
> compiled in a way that uses a non-MT-safe implementation:
>
> $ nm c-strtod.o
> U ___error
> T _c_strtod
> U _free
> U _setlocale
> U _strdup
> U _
On MacOS X 10.5, which has newlocale() and uselocale(), c-strtod is still
compiled in a way that uses a non-MT-safe implementation:
$ nm c-strtod.o
U ___error
T _c_strtod
U _free
U _setlocale
U _strdup
U _strtod$UNIX2003
This fixes it, leading
I'm adding a comment, regarding the encoding of console output on Windows.
2009-12-12 Bruno Haible
* lib/localcharset.c (locale_charset): Add comment about use of GetACP.
*** lib/localcharset.c.orig 2009-12-12 14:45:16.0 +0100
--- lib/localcharset.c 2009-12-12 14:44:39.0
Hi Bruno,
Bruno Haible writes:
>
> > Potential drawback of this approach is that these declarations may affect
> > the implementation as well: there is a risk that compiler may optimize out
> > NULL checks. In other projects where this issue arose before it was
> > worked around by disabling non
