-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8286371: Avoid use of deprecated str[n]icmp #8590
Conversation
👋 Welcome back kbarrett! A progress list of the required criteria for merging this PR into |
@kimbarrett The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
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.
Looks good and trivial.
Thanks.
@kimbarrett This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
Thanks for review @dholmes-ora |
/integrate |
Going to push as commit fe6e0c0.
Your commit was automatically rebased without conflicts. |
@kimbarrett Pushed as commit fe6e0c0. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this trivial change to use _str[n]icmp instead of (deprecated)
str[n]icmp in the only places the latter are used in HotSpot, in
Windows-specific code. This change is in preparation for removing the global
disable of deprecation warnings for HotSpot Windows builds.
An alternative would be to use str[n]casecmp, which are defined in
globalDefinitions_visCPP.hpp for compatibilty in shared code. But since the
uses of the functions being changed are in Windows-specific code I think the
non-deprecated Windows-specific functions are more appropriate.
There are some other uses of the deprecated functions in the JDK. I didn't
change them. Those other places have different approaches to dealing with the
source compatibility and deprecation than does HotSpot, suppressing the
warning for this and various other functions using _CRT_NONSTDC_NO_DEPRECATE.
Note that the deprecation message for these functions is the same one used for
deprecating various POSIX functions, and the deprecation is under the control
of the same macro, even though these aren't actually from POSIX.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8590/head:pull/8590
$ git checkout pull/8590
Update a local copy of the PR:
$ git checkout pull/8590
$ git pull https://git.openjdk.java.net/jdk pull/8590/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8590
View PR using the GUI difftool:
$ git pr show -t 8590
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8590.diff