RFR (T): 8226203: MappedByteBuffer.force method may have no effect on implementation specific map modes

[Andrew Dinn]

Hi Alan,

On 19/06/2019 14:11, Alan Bateman wrote:
> On 19/06/2019 11:07, Andrew Dinn wrote:
>> :
>> Do I still need to wait for confirmation for the CSR from Joe Darcy
>> before pushing to the jdk13 repo? (He already knows about the CSR).
>>
> Yes, anything that has a CSR needs to wait until it is approved.
Joe Darcy has approved the CSR. However, he suggested by way of code
review that the comment be tweaked to explicitly state that the force
method does have an effect when the buffer was mapped with mode
READ_WRITE e.g. instead of

    * <p> This method has no effect for buffers mapped in read-only
    * or private mapping modes. It may also have no effect for other
    * implementation specific map modes. </p>

this

+     * <p> If this buffer was not mapped in read/write mode
+     * ({@link 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>

Would you agree with that change or do you prefer to stick with the
original? If necessary I'll amend the patch and CSR then push whichever
version you prefer to JDK13.

regards,


Andrew Dinn
-----------
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander