> On Apr 19, 2017, at 8:42 PM, John Rose wrote:
>
> On Apr 18, 2017, at 11:42 AM, Dan Smith wrote:
>> I've uploaded a draft of JVMS changes for JEP 181 "Align JVM Checks with
>> Java Language Rules for Nested Classes" to:
>> http://cr.openjdk.java.net/~dlsmith/private-access.html
>
>> classHa
On 20/04/2017 12:46 PM, Brian Goetz wrote:
The way I visualize this is that each newly arrived class
checks in with its host. If the name is on the list, it gets in.
Right, and if it's not on the list? Does it get assigned its own
nest-of-one, or do we reject the class? I would expect the
On 20/04/2017 12:42 PM, John Rose wrote:
On Apr 18, 2017, at 11:42 AM, Dan Smith mailto:daniel.sm...@oracle.com>> wrote:
I've uploaded a draft of JVMS changes for JEP 181 "Align JVM Checks
with Java Language Rules for Nested Classes" to:
http://cr.openjdk.java.net/~dlsmith/private-access.html
On Apr 19, 2017, at 7:46 PM, Brian Goetz wrote:
>
>
>> The way I visualize this is that each newly arrived class
>> checks in with its host. If the name is on the list, it gets in.
>>
>
> Right, and if it's not on the list? Does it get assigned its own
> nest-of-one, or do we reject the cla
The way I visualize this is that each newly arrived class
checks in with its host. If the name is on the list, it gets in.
Right, and if it's not on the list? Does it get assigned its own
nest-of-one, or do we reject the class? I would expect the former? (If
you show up at a party and yo