RE: JavaMemoryModel: Unexpected weakness/divergence in old JVM spec of final fields

From: Bill Pugh (
Date: Mon Jan 05 2004 - 11:40:11 EST

OK, I would be happy with just disallowing classfiles that allow
multiple writes to the same final field. It is certainly simpler than
the alternatives.

But could we get away with requiring that 1.5 verifiers reject such
classfiles, given that the current 1.5 alpha verifier does not?

If not, do we have to say what the semantics are for classfiles that
violate this rule, or can we simply leave it undefined?


This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:56 EDT