https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82922
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #11)
> (In reply to David Brown from comment #9)
> > Could -Wstrict-prototypes be added to -Wall, or even considered enabling by
> > default? The next C standard will make "void foo()" mean the same as "void
> > foo(void)", like in C++, which makes the scope for confusion high.
>
> I think the churn from changing void foo() to void foo(void) to avoid the
> warning is too high, and unnecessary for the upcoming C language change. A
> more target warning could make sense, though.
And even with a more targetted warning we need to be careful about configure
scripts with unprototyped functions.
