While my question is for new functionality I'd like to get in before a 2.0 release, Berin's raises a good point. Is there a whole list of 'things that ought to be done' we could compile for Collections? Then target 2.0 with an aim to clear those up?
Hell, Collections is pretty small, we could go through it a component at a time and solicit opinions, then solve and tick off, then declare 2.0? Is there a list of changes from 1.0 that are being made to 2.0? Should 2.0 enforce a Java 1.2 usage? Just ideas.. Bay On Tue, 19 Feb 2002, Berin Loritsch wrote: > [EMAIL PROTECTED] wrote: > > Where should comparators go by the way? > > > > in > > > > collections.compare > > collections.comparator > > collections > > comparator > > compare > > > If you upgrade to Collections 2.0, then you might as well > upgrade the PriorityQueue interface and implementing classes > to work with Objects instead of Comparables. That was what > the intent was. > > > > -- > > "They that give up essential liberty to obtain a little temporary safety > deserve neither liberty nor safety." > - Benjamin Franklin > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
