-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Useless warnings from gcc -Weffc++ #111
Comments
gcc -Weffc++
Okay, so I should update the Code::Blocks project with it disabled?? I'll see what other warnings I can access. |
Right now we're getting warning-spammed anyways, so for the time being I don't think it does actual damage. Like the OP states, I'm proposing we look how to best replace this flag with some others, so we can get rid of this annoying warning, while keeping the useful ones. If we cannot find good replacements, then I believe it is better to just disable it and accept less compiler-assistance. |
Alright then, that makes a lot more sense, it is rather annoying have five gazillion warnings spat out by the compiler. Also, I'm thinking of moving constructors to the source files instead so it's a bit cleaner, but I'll open another issue for this. |
I still get spurious |
We get some annoying warnings from
-Weffc++
about initializing members via the member initialization list, even though their default constructor is perfectly fine. See GCC Bug 81431 for an upstream bug report, the referenced GCC Bug 16166 is also relevant.We should try to replace this warning with other flags to report things we do want to hear about. At worst we could just get rid of the flag and live with less warnings.
The text was updated successfully, but these errors were encountered: