On Thu, 26 Nov 2020 00:08:37 GMT, Naoto Sato <na...@openjdk.org> wrote:
>> Roger Riggs has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contains 19 additional >> commits since the last revision: >> >> - Clarified that suffix() and prefix() methods do not return null, instead >> the empty string is returned. >> - Merge branch 'master' into 8251989-hex-formatter >> - Merge branch 'master' into 8251989-hex-formatter >> - Merge branch 'master' into 8251989-hex-formatter >> - The HexFormat API indexing model for array and string ranges is changed >> to describe the range using 'fromIndex (inclusive)' and 'toIndex >> (exclusive)'. >> >> Initially, it was specified as 'index' and 'length'. However, both byte >> arrays >> and strings used in the HexFormat API typically use fromIndex and toIndex >> to describe ranges. Using the same indexing model can prevent mistakes. >> >> The change affects the methods and corresponding tests: >> >> formatHex(byte[] bytes, int fromIndex, int toIndex) >> formatHex(A out, byte[] bytes, int fromIndex, int toIndex) >> parseHex(char[] chars, int fromIndex, int toIndex) >> parseHex(CharSequence string, int fromIndex, int toIndex) >> fromHexDigits(CharSequence string, int fromIndex, int toIndex) >> fromHexDigitsToLong(CharSequence string, int fromIndex, int toIndex) >> - - Added @see and @link references to Integer.toHexString and >> Long.toHexString >> - Clarified parsing is case insensistive in various parse and fromXXX >> methods >> - Source level cleanup based on review comments >> - Expanded some javadoc tag text to make it more descriptive >> - Consistent use of 'hexadecimal' vs 'hex' >> - Review comment updates to class javadoc >> - Review comment updates, in the example code, and to describe the >> characters used to convert to hexadecimal >> - Correct length of StringBuilder in formatHex; >> Correct bug in formatHex(char[], 2, 3) and add test for subranges of >> char[] >> - Merge branch 'master' into 8251989-hex-formatter >> - ... and 9 more: >> https://git.openjdk.java.net/jdk/compare/4d7a7098...b19d2827 > > src/java.base/share/classes/java/util/HexFormat.java line 853: > >> 851: */ >> 852: public int fromHexDigit(int ch) { >> 853: int value = Character.digit(ch, 16); > > Do we need to limit parsing the hex digit for only [0-9a-fA-F]? This would > return `0` for other digits, say `fullwidth digit zero` (U+FF10) The normal and conventional characters for hex encoding are limited to the ASCII/Latin1 range. I don't know of any use case that would take advantage of non-ASCII characters. ------------- PR: https://git.openjdk.java.net/jdk/pull/482
