stan/jdk-24
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

8226203: MappedByteBuffer.force method may have no effect on implementation specific map modes

Browse Source 
Fix comment for MappedByteBuffer force methods

Reviewed-by: alanb
This commit is contained in:
Andrew Dinn 2019-06-21 15:16:03 +01:00
parent d1017b71ad
commit 547e919979
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/java.base/share/classes/java/nio/MappedByteBuffer.java
View File

@ -235,8 +235,11 @@ public abstract class MappedByteBuffer
* is made.
*
* <p> If this buffer was not mapped in read/write mode ({@link
* java.nio.channels.FileChannel.MapMode#READ_WRITE}) then invoking this
* method has no effect. </p>
* java.nio.channels.FileChannel.MapMode#READ_WRITE}) then
* invoking this method may have no effect. In particular, the
* method has no effect for buffers mapped in read-only or private
* mapping modes. This method may or may not have an effect for
* implementation-specific mapping modes. </p>
*
* @return This buffer
*/
@ -271,7 +274,10 @@ public abstract class MappedByteBuffer
*
* <p> If this buffer was not mapped in read/write mode ({@link
* java.nio.channels.FileChannel.MapMode#READ_WRITE}) then
* invoking this method has no effect. </p>
* invoking this method may have no effect. In particular, the
* method has no effect for buffers mapped in read-only or private
* mapping modes. This method may or may not have an effect for
* implementation-specific mapping modes. </p>
*
* @param index
* The index of the first byte in the buffer region that is