[concurrency-interest] weakCompareAndSet in atomics - incompatible class change?
dawidk at mathcs.emory.edu
Sat Mar 3 15:45:04 EST 2007
Question: isn't adding a final method to a non-final class an
incompatible class change? It breaks subclasses containing a method with
the same signature. What's the official view on this?
This is what happened with Atomic* classes: in 6.0, weakCompareAndSet()
method was added. As a result, the backport-util-concurrent optimized
for 5.0, in which the "backport" atomics extend native atomics, does not
work on 6.0. (I always thought that Atomic* classes should have been
made final :P )
More information about the Concurrency-interest