Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 44638 invoked from network); 19 Feb 2002 16:53:09 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 19 Feb 2002 16:53:09 -0000 Received: (qmail 16628 invoked by uid 97); 19 Feb 2002 16:53:10 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 16587 invoked by uid 97); 19 Feb 2002 16:53:09 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 16576 invoked from network); 19 Feb 2002 16:53:09 -0000 Message-ID: <3C7283A9.5050306@apache.org> Date: Tue, 19 Feb 2002 11:56:09 -0500 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204 X-Accept-Language: en-us MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: Collections 2.0? (Collections 1.1 RIP) References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N bayard@generationjava.com 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: For additional commands, e-mail: