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

[Maurizio Cimadamore]

On Fri, 23 Sep 2022 15:31:47 GMT, Jorn Vernee <jvernee at openjdk.org> wrote:

>> I think for regular Java developers, there is probably a much less clear distinction between heap/off-heap and "physical" memory in the first place.
>> 
>> i.e. if heap memory is the part of memory that is used to store Java objects, and off-heap is the part of memory that _isn't_ used to store Java objects, then I guess "physical memory" is just all of memory combined? Maybe just saying "memory" is enough? In the above, that could make:
>> 
>>     The {@linkplain #address() address} of a native segment (including mapped segments) denotes the starting address of the region of memory which backs the segment.
>
> 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.

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

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