[core-libs] RFR (L): 8010319: Implementation of JEP 181: Nest-Based Access Control

[David Holmes]

Hi Peter,

On 21/05/2018 4:12 PM, Peter Levart wrote:
> 
> 
> On 05/21/2018 07:57 AM, David Holmes wrote:
>> Do we really need to spell out the case for primitives and arrays? If 
>> so would it suffice to add the following:
>>
>> "A class or interface that is not explicitly a member of a nest *(such 
>> as primitive or array classes)*, is a member of the nest consisting 
>> only of itself, and is the nest host. Every class and interface is a 
>> member of exactly one nest." 
> 
> That's fine, but then someone might wonder whether only primitive and 
> array classes are not explicit members of a nest.
> 
> What about:
> 
> "A class or interface that is not explicitly a member of a nest 
> *(including but not limited to primitive and array classes)*, is a 
> member of the nest consisting only of itself, and is the nest host. 
> Every class and interface is a member of exactly one nest."

But "including but not limited to" is just a more verbose way of saying 
"such as". "such as x" introduces an example case x, hence "including 
x", but is not exhaustive and so covers "not limited to x".

David
-----

> Regards, Peter
>