Created https://issues.apache.org/jira/browse/COLLECTIONS-233
Stephen Kestle wrote:
I shall be opening a ticket for the Closure one in the next while
(when I get a chance).
Note that Procedure and Function don't actually say anything - they're
very broad programming principals. Also note tha
If only I had more than +1 vote!
Stephen Colebourne wrote:
There has been reltively little feedback on these backwards
incompatible changes. Do I assume (by lazy consensus) that
[collections-generics] will be seriously backwards incompatible? Can I
commit changes? Are we agreed on the strategy
On 11/3/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
There has been reltively little feedback on these backwards incompatible
changes. Do I assume (by lazy consensus) that [collections-generics]
will be seriously backwards incompatible? Can I commit changes? Are we
agreed on the strategy "pr
+1
Better to break compatibility upfront as part of an explicit design
decision, than to see it slowly wither away.
--
Stephen Smith, MEng (Wales).
http://www.stephen-smith.co.uk/
Stephen Colebourne wrote:
There has been reltively little feedback on these backwards incompatible
changes. Do I
There has been reltively little feedback on these backwards incompatible
changes. Do I assume (by lazy consensus) that [collections-generics]
will be seriously backwards incompatible? Can I commit changes? Are we
agreed on the strategy "produce the best API", rather than "produce a
compatible A
I shall be opening a ticket for the Closure one in the next while (when
I get a chance).
Note that Procedure and Function don't actually say anything - they're
very broad programming principals. Also note that a Factory may not
actually create/generate something (it may already be in the ware
On Sat, 28 Oct 2006, Stephen Colebourne wrote:
> First analysis of the collection subpackage of [collections] for the
> generics branch.
>
> - BoundedCollection should be deleted/renamed to Bounded
> new Bounded interface would not implement Collection, allowing it to be
> implemented by Maps as w
On 10/27/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
First analysis of the collection subpackage of [collections] for the
generics branch.
- BoundedCollection should be deleted/renamed to Bounded
new Bounded interface would not implement Collection, allowing it to be
implemented by Maps as
First analysis of the collection subpackage of [collections] for the
generics branch.
- BoundedCollection should be deleted/renamed to Bounded
new Bounded interface would not implement Collection, allowing it to be
implemented by Maps as well as Collections
- UnmodifiableBoundedCollection sho
