GCC 6 Will Warn You About Misleading Code Indentations

[phoronix]

Phoronix: GCC 6 Will Warn You About Misleading Code Indentations

As reminded this weekend by Red Hat developer Mark Wielaard, GCC 6 will warn you about misleading code indentations...

http://www.phoronix.com/scan.php?page=news_item&px=GCC6-Misleading-Indentation

[tomtomme]

I bet openSUSE Tumbleweed will get this earlier than Fedora

[Del_]

and both Debian testing and unstable even before that ;-)

[Michael]

and both Debian testing and unstable even before that ;-)

I guess I should have phrased it better, was implying about released/stable distribution releases

[carewolf]

I guess I should have phrased it better, was implying about released/stable distribution releases

Debian unstable is basically a stable rolling release. The prerelease stuff is in experimental. You can already get gcc-6 there.

[GreatEmerald]

Debian unstable is basically a stable rolling release. The prerelease stuff is in experimental. You can already get gcc-6 there.

Michael said "released/stable", AKA not rolling release.

[armetuz]

Debian unstable is basically a stable rolling release

I found that unstable is very buggy. Personally I prefer Arch that gives me less problems.

[waxhead]

Debian unstable is basically a stable rolling release. The prerelease stuff is in experimental. You can already get gcc-6 there.

I use Debian daily and while TESTING can be considered a mostly stable rolling release I would not say the same about unstable, neither would Debian that's why they name it unstable. Testing on the other hand is very stable and have not given me much trouble at all as long as you pay some attention to what happens to your packages during updates!

[haagch]

Heh, I was wondering about whether it would be a good idea to have such a warning after seeing http://lists.freedesktop.org/archive...ne/086773.html. I guess it is.

[waxhead]

Heh, I was wondering about whether it would be a good idea to have such a warning after seeing http://lists.freedesktop.org/archive...ne/086773.html. I guess it is.

You can always improve warnings. And in this case a always return false is fixed by adding the missing braces. I on the other hand prefer braces on separate lines and that also introduce problems.

For example a typo like if(whatever); will cause the block to never get executed while if(whatever){; does not matter at all. Not sure if GCC have warning for this , but I sure would like to have that in too