8246282: [REDO] JDK-8245121 (bf) XBuffer.put(Xbuffer src) can give unexpected result when storage overlaps
Alan Bateman
Alan.Bateman at oracle.com
Thu Jun 4 18:30:26 UTC 2020
On 04/06/2020 16:10, Brian Burkhalter wrote:
>
> --- a/src/java.base/share/classes/java/nio/X-Buffer.java.template
> +++ b/src/java.base/share/classes/java/nio/X-Buffer.java.template
> @@ -1499,10 +1499,10 @@
>
>
> #if[char]
> /**
> - * Tells whether this buffer has simply addressable memory, e.g.,
> - * a Java array or a native address. This method returns {@code
> true}.
> - * Subclasses which do not have simply addressable memory should
> override
> - * this method to return {@code false}.
> + * Tells whether this buffer has addressable memory, e.g., a Java
> array or
> + * a native address. This method returns {@code true}.
> Subclasses such as
> + * {@code StringCharBuffer}, which wraps a {@code CharSequence},
> should
> + * override this method to return {@code false}.
> *
> * @return {@code true} if, and only, this buffer has addressable
> memory
> */
>
Thanks, this works for me.
-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/nio-dev/attachments/20200604/869158c4/attachment.htm>
More information about the nio-dev
mailing list