> "Sergio" == Sergio Durigan Junior writes:
> Another possibility that may be simpler for GDB, is to change its
> configure.ac files to require C99 or later everywhere. At this point
> it's more trouble than it's worth to tweak source code or makefiles to
> cater to compilers operatin
On Friday, August 31 2018, Tom Tromey wrote:
>> "Sergio" == Sergio Durigan Junior writes:
>
"CC=$(CC)" \
"CFLAGS=$(CFLAGS)" \
"CXX=$(CXX)" \
"CXX_DIALECT=$(CXX_DIALECT)" \
"CXXFLAGS=$(CXXFLAGS)" \
...
>
Which ends up overriding gnulib's CC/CXX variables. Th
> "Sergio" == Sergio Durigan Junior writes:
>>> "CC=$(CC)" \
>>> "CFLAGS=$(CFLAGS)" \
>>> "CXX=$(CXX)" \
>>> "CXX_DIALECT=$(CXX_DIALECT)" \
>>> "CXXFLAGS=$(CXXFLAGS)" \
>>> ...
>>> Which ends up overriding gnulib's CC/CXX variables. That's why we don't
>>> see the "-std=gnu11" there.
>> Ma
Simon Kobyda wrote:
> It seems that functions gnulib's functions iswprint() and
> wcwidth() return different results on different platforms.
>
> Code on Fedora 28:
>
> wchar_t c = L'😀' ;
> if (iswprint(c))
> printf("Printable\n");
> else
> printf("Not printable\n");
>
Hi Paul,
(sorry for the long delay)
Le Wed, 1 Aug 2018 23:45:08 -0700, Paul Eggert
a écrit :
> Albert ARIBAUD wrote:
> > I really need you to develop in some more detail how you envision adding
> > Y2038 support in Gnulib.
>
> It sounds like the best thing to do is the original plan: you dev
Simon Kobyda wrote:
Hello. It seems that functions gnulib's functions iswprint() and
wcwidth() return different results on different platforms.
Surely this is an issue of the platform's locales, not of Gnulib itself. Older
platforms won't recognize newer characters, and some locales are simply
Hello. It seems that functions gnulib's functions iswprint() and
wcwidth() return different results on different platforms.
Code on Fedora 28:
wchar_t c = L'😀' ;
if (iswprint(c))
printf("Printable\n");
else
printf("Not printable\n");
Output: "Printable"
Code on CentO
