-
Notifications
You must be signed in to change notification settings - Fork 602
Silence warnings in win32/win32.c #21925
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
Conversation
win32/win32.c
Outdated
| PERL_UNUSED_ARG(hwnd); | ||
| PERL_UNUSED_ARG(lParam); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These arguments are used and I don't see a warning for them.
We probably need to add
The code that uses this is conditional on I'm not sure about gets(). |
|
I've added Is there anything I should try at this stage to deal with any of those remaining warnings ? |
|
The The definition of wstr_to_str() and probably the declaration at the top should be in The use of gets() could be surrounded by GCC_DIAG_IGNORE_STMT(): |
|
Having built perl with |
|
I have prepared other files to avoid issuing of pointless warnings - including the removal of 650 lines of such warnings from win32/perlhost.h. |
|
Please squash the 3 commits here into one commit. Please add the perlhost fixes to a new PR. Thanks |
44d4b29 to
331d832
Compare
|
I think I've succeeded in squashing the 3 commits into 1. |
In win32/win32.c, this PR silences numerous
[-Wunused-parameter]and[-Wunused-variable]warnings; also a[-Wsign-compare], a[-Wdangling-else]and a[-Wparentheses]warning.The following warnings remain:
I have queries about the best way to deal with those remaining warnings, and I'm thinking if we can just pick the low hanging fruit for now, it will make it easier to deal with those remaining issues later on.
My
perl -Voutput is: