[foreign-memaccess+abi] RFR: 8292034: Improve javadoc after memory segment/memory address unification [v2]

[Maurizio Cimadamore]

On Fri, 23 Sep 2022 15:46:33 GMT, Maurizio Cimadamore <mcimadamore at openjdk.org> wrote:

>> If none of these options seem better to you though, I don't mind sticking with "physical address/memory".
>
> I think `physical memory` is the problem, more so than `physical address`. We can explain `physical address` as something different from `MemorySegment::address`, but I don't think we need a qualifier for memory.

I looked at this again, and decided to leave as is. `MappedByteBuffer` is also quite full of references to terms like `physical memory` (which we inherited in methods like `MemorySegment::isLoaded`.

-------------

PR: https://git.openjdk.org/panama-foreign/pull/730