[concurrency-interest] DirectByteBuffers and reachabilityFence

David Holmes davidcholmes at aapt.net.au
Thu Dec 10 16:06:15 EST 2015

David M. Lloyd writes:
> On 12/09/2015 07:44 PM, David Holmes wrote:
> > To be clear, I missed this later assertion:
> >
> >> In summary, we agree that an object can _become finalizable_ before
> >> completion of its constructor, if the Object constructor completed
> >> normally and the object is otherwise no longer reachable.
> >
> > No! The object should not be able to become finalizable until after
> all its
> > constructors have completed, and then it becomes unreachable.
> Is this your view of the existing world, or what you are proposing be
> changed?  I'm losing track of what's what in this discussion. :-)

This is how the existing world should have been if the JLS update had not
been snafu'd. Justin would argue it should be the current state regardless
due to happens-before definition. Regardless the JVM does not currently
implement this.

David H.

> --
> - DML
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest

More information about the Concurrency-interest mailing list