Skip to content
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

Open
z33ky opened this issue Aug 24, 2017 · 4 comments
Open

Useless warnings from gcc -Weffc++ #111

z33ky opened this issue Aug 24, 2017 · 4 comments
Projects

Comments

@z33ky
Copy link
Collaborator

z33ky commented Aug 24, 2017

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.

@z33ky z33ky changed the title Useless warnings from gcc -Weffc++ Useless warnings from gcc -Weffc++ Aug 24, 2017
@Quaker762
Copy link
Member

Okay, so I should update the Code::Blocks project with it disabled?? I'll see what other warnings I can access.

@z33ky
Copy link
Collaborator Author

z33ky commented Aug 29, 2017

Right now we're getting warning-spammed anyways, so for the time being I don't think it does actual damage.
I believe most warnings are reasonably fixable in code. The member-initialization warnings of -Weffc++ look 100% spurious though, but there are other warnings enabled with that same flag that are useful.

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.

@Quaker762
Copy link
Member

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.

@Quaker762 Quaker762 added this to Done in TODO Feb 20, 2018
@z33ky
Copy link
Collaborator Author

z33ky commented Feb 21, 2018

I still get spurious -Weffc++ warnings; I don't think this is "Done".

@Quaker762 Quaker762 moved this from Done to In progress in TODO Feb 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
TODO
  
In progress
Development

No branches or pull requests

2 participants