arn...@skeeve.com writes:
>> At this point I wouldn't worry about the older clang and gcc versions
>> that complain about {0} as an initializer. We can either let them die
>> off noisily, or use the appropriate -Wno-whatever option when using them
>> to compile.
>
> I've decided to just not wor
Paul Eggert wrote:
> On 5/27/21 1:46 PM, Eric Blake wrote:
>
> > Yet another portable solution is:
> >
> > static mbstate_t s1;
> > mbstate_t s = s1;
> >
> > also with its own form of ugliness.
>
> I did that years ago, but compilers complained about it when I made s1
> 'const', and I vaguely
On 5/27/21 1:46 PM, Eric Blake wrote:
Yet another portable solution is:
static mbstate_t s1;
mbstate_t s = s1;
also with its own form of ugliness.
I did that years ago, but compilers complained about it when I made s1
'const', and I vaguely recall complaints even when it wasn't 'const'
("W
On Wed, May 12, 2021 at 12:16:54PM +0200, Bruno Haible wrote:
> > > dfa.c:1627:19: warning: suggest braces around initialization of subobject
> > > [-Wmissing-braces]
> > > mbstate_t s = { 0 };
> > > ^
> > > {}
> > > 1 warning generated.
>
> { 0 } is the
Hi Arnold,
> > OSX 10.11.6
> > Building after using 'touch .developing' for the first time, I get
> >
> > depbase=`echo dfa.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> > gcc -DGAWK -DHAVE_CONFIG_H -I"./.." -I. -I.. -I/opt/local/include
> > -I/opt/local/include -g -O2 -DARRAYDEBUG -DYYDEBUG -DLOCAL
