Moving from VVT to the L-world value types (LWVT) (original) (raw)
Paul Sandoz paul.sandoz at oracle.com
Thu Feb 1 17:49:30 UTC 2018
- Previous message (by thread): Moving from VVT to the L-world value types (LWVT)
- Next message (by thread): Moving from VVT to the L-world value types (LWVT)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 1, 2018, at 5:57 AM, John Rose <john.r.rose at oracle.com> wrote:
On Jan 29, 2018, at 7:31 PM, Frederic Parain <frederic.parain at oracle.com> wrote: During a brainstorming session with Karen this morning, we realized that case 2-A (ACCFLAT flag set for an object class) should be in fact treated as an error, instead of just ignoring the flag. I agree, this is a cleaner option, better than saying "oops, not flat after all". Using Remi's notation, the choice is between: ACCNONNULLABLEANDERRORIFOBJECTTYPE or: ACCNONNULLABLEUNLESSOBJECTTYPE Also, forbidding this configuration leaves open, as a future option, the ability of a classfile to specify non-nullable reference fields. That is potentially useful, depending on the future fortunes of null (that billion-dollar mistake).
Yes, i was opportunistically thinking the same thing when asking questions related to enums.
Paul.
- Previous message (by thread): Moving from VVT to the L-world value types (LWVT)
- Next message (by thread): Moving from VVT to the L-world value types (LWVT)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]