Date: Wed, 7 Mar 2018 10:44:14 -0500 From: Ed Maste <emaste@freebsd.org> To: Eitan Adler <eadler@freebsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r330602 - head/sys/compat/cloudabi Message-ID: <CAPyFy2DOrHNs2BEQVqJYBGxT4iiA3ms_crXcX=q0wXr=63ddug@mail.gmail.com> In-Reply-To: <201803071447.w27Elh7C053393@repo.freebsd.org> References: <201803071447.w27Elh7C053393@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7 March 2018 at 09:47, Eitan Adler <eadler@freebsd.org> wrote: > Author: eadler > Date: Wed Mar 7 14:47:43 2018 > New Revision: 330602 > URL: https://svnweb.freebsd.org/changeset/base/330602 > > Log: > sys/cloudabi: Avoid relying on GNU specific extensions > > An empty initializer list is not technically valid C grammar. > > MFC After: 1 week > > - cloudabi_fdstat_t fsb = {}; > + cloudabi_fdstat_t fsb = {0}; In practice it appears initializing via { 0 } also zeros any padding in the struct, but I do not believe it's required by the C standard. Perhaps a language lawyer can weigh in? Commenting on this commit just because it's highlighted by this change; I do not believe there's a difference between the GNU extension { } and { 0 } here.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DOrHNs2BEQVqJYBGxT4iiA3ms_crXcX=q0wXr=63ddug>