commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <scolebou...@btopenworld.com>
Subject [collections] Binary compatability for v3.1
Date Sun, 02 May 2004 23:52:57 GMT
Currently, as far as I can tell there are two binary incompatible changes on
the CVS for v3.1 over v3.0.

1) ReferenceMap (map package) now extends AbstractReferenceMap and
AbstractHasedMap whereas previously it extended AbstractMap. This was done
to gain lots of new functionality.

This is binary incompatible if you previously cast a ReferenceMap to an
AbstractMap. There is no good reason why you would have made this cast, so I
am in favour of allowing this change.

2) FixedSizeSortedMap now extends FixedSizeMap whereas previously it
extended AbstractSortedMapDecorator. This was done to share more code.

This is binary incompatible if you previously cast a FixedSizeSortedMap to
an AbstractSortedMapDecorator. There is no good reason why you would have
made this cast, so I am in favour of allowing this change.


Does anyone else have opinions on this? There are ways around both if
necessary. How far should we go on this kind compatability?

Stephen


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message