Re: Warning for C Parameter Name Mismatch

2019-03-09 Thread Jonathan Wakely
On Sat, 9 Mar 2019, 02:23 Eric Gallager, wrote: > On 3/8/19, David Brown wrote: > > On 09/03/2019 00:06, Joseph Myers wrote: > >> On Fri, 8 Mar 2019, Joel Sherrill wrote: > >> > >>> Can gcc report when the parameter name in a C prototype > >>> does not match that used in the implementation? > >>

Re: Warning for C Parameter Name Mismatch

2019-03-09 Thread David Brown
On 09/03/2019 03:23, Eric Gallager wrote: On 3/8/19, David Brown wrote: On 09/03/2019 00:06, Joseph Myers wrote: On Fri, 8 Mar 2019, Joel Sherrill wrote: Can gcc report when the parameter name in a C prototype does not match that used in the implementation? int f(int x); int f(int y) {.

Re: Warning for C Parameter Name Mismatch

2019-03-09 Thread Segher Boessenkool
On Sat, Mar 09, 2019 at 08:30:19AM +, Jonathan Wakely wrote: > On Sat, 9 Mar 2019, 02:23 Eric Gallager, wrote: > > How would it handle the case where the parameter name is missing > > entirely from the prototype? I see a lot of header files with their > > prototypes written like that. > > > >

Re: Warning for C Parameter Name Mismatch

2019-03-09 Thread Joel Sherrill
On Sat, Mar 9, 2019, 11:27 AM Segher Boessenkool wrote: > On Sat, Mar 09, 2019 at 08:30:19AM +, Jonathan Wakely wrote: > > On Sat, 9 Mar 2019, 02:23 Eric Gallager, wrote: > > > How would it handle the case where the parameter name is missing > > > entirely from the prototype? I see a lot of

合C法R经f营W

2019-03-09 Thread ptzv
办QO   理  $   +Q+V+信/-   -- &   $  -- I 3 4 髮  $---  2 4 3 4   &   $  ---6 1 4 8 漂 $  -2019/3/10

Re: Warning for C Parameter Name Mismatch

2019-03-09 Thread Basile Starynkevitch
(I am reading the GCC mailing list in digest mode) On 3/9/19 10:58 PM, gcc-digest-h...@gcc.gnu.org wrote: On Fri, 8 Mar 2019, Joel Sherrill wrote: Can gcc report when the parameter name in a C prototype does not match that used in the implementation? int f(int x); int f(int y) {...} I t