-
Notifications
You must be signed in to change notification settings - Fork 149
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
Unused parameters in XrdSecInterface.hh #337
Comments
Hi, Could you please give details on the OS and its version and on the compiler and its version? Thanks, Gerardo GANIS On 22 Feb 2016, at 16:42, Bastian Beischer notifications@github.com wrote:
|
This is with Arch Linux x86_64, GCC 5.3.0. g++ --version gives:
Anything else? :) |
Hi Bastian, Ah, yes, I thought we had corrected those everywhere they occur. Andy On Mon, 22 Feb 2016, Bastian Beischer wrote:
|
See this PR: #323 |
Yes, I can understand why this PR added the parameters back for doxygen. Unfortunately I think there's no way to refer to the parameter names in the doxygen docu using 'param[in]' etc when the actual parameter names are removed / commented out, safe for preprocessor magic just for doygen (#ifdef DOXYPROCESSING - see also http://doxygen.10944.n7.nabble.com/commented-function-parameters-td3718.html) You could of course (void) cast the unused arguments before returning ENOTSUP... |
Yes, void casting is the way to go. |
Yes, I see now what happened. A patch witn unintended side-effects. This Andy On Mon, 22 Feb 2016, Lukasz Janyst wrote:
|
I'm getting the following warnings when building ROOT against xrootd version ae07ce1 (master branch)
It would be great if these could be fixed.
The text was updated successfully, but these errors were encountered: