Re: [PATCH] refspec.h: reinstate 'extern' to fix sparse warning
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 16, 2018, 21:52 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1805162351050.77@tvgsbejvaqbjf.bet>
- In-Reply-To
- <CAGZ79kbPNJPtcvbgu81y3UYmKsUd6UNNr9kmQ7qjEfB0ZBTJwQ@mail.gmail.com>
On Wed, 16 May 2018, Stefan Beller wrote:
Show 10 quoted lines
> On Wed, May 16, 2018 at 2:42 PM, Brandon Williams <bmwill@google.com> wrote: > > > Though now I'm confused, I thought we were going towards eliminating > > using the extern keyword? ...of course I guess it means something > > _slightly_ different when using with a variable vs a function :) > > We're only eliminating it when it is redundant. :-) > > For variables this is not redundant as we need it to tell apart the > declaration and definition of it, so we have to keep it.
Otherwise we will end up with the variable *defined* for every file that includes that header. And of course those different versions of the same variable would have possibly different values...