On Tue, Dec 22, 2015 at 12:33:51PM -0500, Patrick Palka wrote:
> We are emitting a bogus warning for the code
>
> do foo (0); while (flagA);
> ^--- NEXT
> ^ BODY
> ^--- GUARD
>
> In general I don't think we can get any useful indentation warning out
On 01/08/2016 03:43 AM, Jakub Jelinek wrote:
On Tue, Dec 22, 2015 at 12:33:51PM -0500, Patrick Palka wrote:
We are emitting a bogus warning for the code
do foo (0); while (flagA);
^--- NEXT
^ BODY
^--- GUARD
In general I don't think we can
On 01/05/2016 10:58 PM, David Malcolm wrote:
In general I don't think we can get any useful indentation warning out
of a do-while statement, so this patch makes it so that we just skip
them.
Is this OK to commit after testing?
It looks like this is PR c++/69029. FWIW, I agree with your
On Tue, 2015-12-22 at 12:33 -0500, Patrick Palka wrote:
> We are emitting a bogus warning for the code
>
> do foo (0); while (flagA);
> ^--- NEXT
> ^ BODY
> ^--- GUARD
>
> In general I don't think we can get any useful indentation warning out
> of a
We are emitting a bogus warning for the code
do foo (0); while (flagA);
^--- NEXT
^ BODY
^--- GUARD
In general I don't think we can get any useful indentation warning out
of a do-while statement, so this patch makes it so that we just skip
them.
Is
This patch fixes the last remaining false-positive
-Wmisleading-indentation warning that is emitted against the sqlite
sources.
The problem is the following kind of code snippet:
for (i = 0;
i < 10;
i++
);
foo (i);
which is an "interesting" coding style but it is
On 09/21/2015 01:23 PM, Patrick Palka wrote:
* c-indentation.c (should_warn_for_misleading_indentation):
Float out and consolidate the calls to get_visual_column that is
passed guard_exploc as an argument. Compare
next_stmt_vis_column with guard_line_first_nws
