> Well, if you write code so obvious that -Wuninitialized is annoying then:
No, the code is certainly not obvious, and improving -Wuninitialized although a nice goal is likely to require lots of effort, likely at the expense of removing some useful warnings. > either the implementation of -Wuninitialized should be improved, or as you You can't have it both ways: either -Wuninitialized is indeed improved to the point where it generates almost no false positives, and then enabling it by default should be considered/done; or -Wuninitialized does generate false positives and enabling it by default is likely not a good idea. Same for -Wmaybe-uninitialized, also part of -Wall. > are so expert that you can add -Wno-uninitialized. I think the argument > cuts both ways. Who said anything about being "so expert"? IMO that's precisely non experts who will get the most annoyed here, because they may not understand why the warning is generated, nor how to disable it. And IMO, a discussion about a "default" is certainly NOT about experts, it's precisely a discussion about what would be the best default for most people (and most people are not experts). Arno
