Subject: Re: bug#11675: stty bad C semantics

From: Eric Blake <[email-masked]>
Date: Tue, 12 Jun 2012 08:58:13 -0600

On 06/12/2012 08:52 AM, Voelker, Bernhard wrote:
> Jim Meyering wrote:
> 
>> That has prompted a nicely animated debate ;-)
> 
> ... and it goes on ;-)
> 
> What about these?
> 
> find . -name '*.c' | xargs grep -F '0, };'
> ./src/ls.c:                    mbstate_t mbstate = { 0, };
> ./src/shred.c:  struct Options flags = { 0, };
> ./src/tr.c:  bool in_set[N_CHARS] = { 0, };
> ./src/wc.c:      mbstate_t state = { 0, };
> ./src/pathchk.c:      mbstate_t mbstate = { 0, };

What about them?  None of them are using memcmp(), so none of them care
what the padding bytes (if any) got set to.

-- 
Eric Blake   [email-masked]    +1-919-301-3266
Libvirt virtualization library http://libvirt.org