There were two issues with this sequence in the resulting HTML pages. The first
one, which you mentioned and fixed, was a missing zero. The second one, which
you fixed but didn't mention, was an extra slash symbol.
Looks good to me.
P.S. There seem to be more cases where authors assumed the contents of the
{@code} inline tags are not in any way interpreted. While this is certainly
true for HTML entities and special symbols, it doesn't eliminate translation of
\uxxxx sequences performed by the compiler.
-Pavel
> On 29 May 2020, at 10:37, Conor Cleary <conor.cle...@oracle.com> wrote:
>
> Hi,
>
> Could someone please review my webrev for JDK-8245658 'Arrays.java has two
> occurrences of bad unicode constants in Javadoc.'?
>
> In Arrays.java Javadoc, there were two instances of bad Unicode formatting
> where the null character constant was incorrectly specified with '\u000'
> (another zero is required). This fix displays the correct Unicode constants
> in the Javadoc so that outputted docs display '\u0000'.
>
> bug: https://bugs.openjdk.java.net/browse/JDK-8245658
> webrev:
> http://cr.openjdk.java.net/~pconcannon/ccleary/8245658/webrevs/webrev.01/
>
>
> Regards,
> Conor
>
