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

Consider disabling -Wunused-parameter in compilation #377

Closed
stephentu opened this issue Jan 11, 2015 · 2 comments
Closed

Consider disabling -Wunused-parameter in compilation #377

stephentu opened this issue Jan 11, 2015 · 2 comments

Comments

@stephentu
Copy link
Contributor

I switched over from gcc to clang for my default C++ compiler, and clang is pretty verbose by default about unused parameters.

We can either fix these warnings or compile with -Wno-unused-parameter. Either is fine by me, but I'm more inclined towards the latter since I think unused parameters is no big deal.

@rcurtin
Copy link
Member

rcurtin commented Jan 12, 2015

In 3ad083b I've fixed the -Wunused-parameter warnings. They don't appear under gcc, but I think this may be because gcc might not issue warnings for functions it isn't actually compiling into something. Just a guess though. I fixed some -Wunused-private-field warnings in fba66e1 and 660fd96. With those fixes, do you still see warnings? (Maybe at the level of Armadillo?)

Personally I like fixing warnings, in case downstream projects are compiling with aggressive warning settings (I think RcppMLPACK compiles with -pedantic? I'm not certain though).

@stephentu
Copy link
Contributor Author

Ok, clang is now quiet on a clean build. Thanks! Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants