OK.
On Sun, Oct 30, 2016 at 3:53 PM, Mark Wielaard wrote:
> On Tue, Oct 25, 2016 at 01:57:09AM +0200, Mark Wielaard wrote:
>> I think the only thing "blocking" the patch from going in is that
>> nobody made a decission on how the actual warning option should be
>> named. I think the suggestion fo
On Tue, Oct 25, 2016 at 01:57:09AM +0200, Mark Wielaard wrote:
> I think the only thing "blocking" the patch from going in is that
> nobody made a decission on how the actual warning option should be
> named. I think the suggestion for -Wshadow=[global|local|compatible-local]
> is the right one. Wi
On Mon, Oct 24, 2016 at 04:26:49PM -0700, Jim Meyering wrote:
> I have been using these new options (locally patched) to good effect.
> While the vast majority of warning-triggering code has been
> technically correct, using these has uncovered at least 4 or 5 real
> bugs in code I care about.
Awe
On Wed, Sep 14, 2016 at 5:49 AM, Mark Wielaard wrote:
> On Wed, 2016-09-14 at 05:39 -0700, Ian Lance Taylor wrote:
>> On Wed, Sep 14, 2016 at 1:30 AM, Mark Wielaard wrote:
>> > On Wed, 2016-09-14 at 00:00 -0400, Jason Merrill wrote:
>> >> I wonder about spelling the options as
>> >> -Wshadow={loc
On Wed, 2016-09-14 at 05:39 -0700, Ian Lance Taylor wrote:
> On Wed, Sep 14, 2016 at 1:30 AM, Mark Wielaard wrote:
> > On Wed, 2016-09-14 at 00:00 -0400, Jason Merrill wrote:
> >> I wonder about spelling the options as
> >> -Wshadow={local,compatible-local} rather than with a dash, but
> >> otherw
On Wed, Sep 14, 2016 at 1:30 AM, Mark Wielaard wrote:
> On Wed, 2016-09-14 at 00:00 -0400, Jason Merrill wrote:
>> I wonder about spelling the options as
>> -Wshadow={local,compatible-local} rather than with a dash, but
>> otherwise the patch looks fine.
>
> That is a much nicer way to write the o
On 9/14/16, Jason Merrill wrote:
> On Mon, Sep 12, 2016 at 1:38 PM, Jim Meyering wrote:
>> On Mon, Sep 12, 2016 at 7:05 AM, Eric Gallager
>> wrote:
>>> On 9/11/16, Manuel López-Ibáñez wrote:
On 11/09/16 14:02, Mark Wielaard wrote:
> -Wshadow-local which warns if a local variable shad
On Wed, 2016-09-14 at 00:00 -0400, Jason Merrill wrote:
> I wonder about spelling the options as
> -Wshadow={local,compatible-local} rather than with a dash, but
> otherwise the patch looks fine.
That is a much nicer way to write the option. But if I do that I would
like to keep the old names as a
On Mon, Sep 12, 2016 at 1:38 PM, Jim Meyering wrote:
> On Mon, Sep 12, 2016 at 7:05 AM, Eric Gallager wrote:
>> On 9/11/16, Manuel López-Ibáñez wrote:
>>> On 11/09/16 14:02, Mark Wielaard wrote:
-Wshadow-local which warns if a local variable shadows another local
variable or parame
On Mon, Sep 12, 2016 at 7:05 AM, Eric Gallager wrote:
> On 9/11/16, Manuel López-Ibáñez wrote:
>> On 11/09/16 14:02, Mark Wielaard wrote:
>>> -Wshadow-local which warns if a local variable shadows another local
>>> variable or parameter,
>>>
>>> -Wshadow-compatible-local which warns if a lo
On 9/11/16, Manuel López-Ibáñez wrote:
> On 11/09/16 14:02, Mark Wielaard wrote:
>> -Wshadow-local which warns if a local variable shadows another local
>> variable or parameter,
>>
>> -Wshadow-compatible-local which warns if a local variable shadows
>> another local variable or parameter
Hi Manuel,
On Sun, Sep 11, 2016 at 08:26:20PM +0100, Manuel López-Ibáñez wrote:
> On 11/09/16 14:02, Mark Wielaard wrote:
> > -Wshadow-local which warns if a local variable shadows another local
> > variable or parameter,
> >
> > -Wshadow-compatible-local which warns if a local variable sha
On 11/09/16 14:02, Mark Wielaard wrote:
-Wshadow-local which warns if a local variable shadows another local
variable or parameter,
-Wshadow-compatible-local which warns if a local variable shadows
another local variable or parameter whose type is compatible with that
of the shadowing
13 matches
Mail list logo
