-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8262351: Extra '0' in java.util.Formatter for '%012a' conversion with a sign character #2881
8262351: Extra '0' in java.util.Formatter for '%012a' conversion with a sign character #2881
Conversation
👋 Welcome back igraves! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
This all looks fine - just update the copyright year in Formatter.java, please.
In my personal opinion, this behavior change does not rise to the level of needing a CSR, but since it is long-standing behavior, you might double-check with Joe.
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 to me.
BTW apart from this issue, I just noticed that in the chart in the Formatter
class spec, there are two spaces (two NBSPs) for the extra space
flag:
* <tr><th scope="row" style="vertical-align:top"> <code>' '</code>
* <td style="vertical-align:top"> <code>'\u0020'</code>
* <td> Requires the output to include a single extra space
* (<code>'\u0020'</code>) for non-negative values.
*
* <p> If both the {@code '+'} and <code>' '</code> flags are given
* then an {@link IllegalFormatFlagsException} will be thrown.
This might be fixed sometime.
@igraves 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 35 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@bchristi-git, @naotoj) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/csr |
@igraves has indicated that a compatibility and specification (CSR) request is needed for this pull request. |
/integrate |
/sponsor |
@bchristi-git @igraves Since your change was applied there have been 36 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 6971c23. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This fixes a zero-adding issue observed in the hex float conversion.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2881/head:pull/2881
$ git checkout pull/2881