Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 64130 invoked from network); 9 Aug 2006 23:39:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Aug 2006 23:39:31 -0000 Received: (qmail 23232 invoked by uid 500); 9 Aug 2006 23:39:29 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 22952 invoked by uid 500); 9 Aug 2006 23:39:28 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 22941 invoked by uid 99); 9 Aug 2006 23:39:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2006 16:39:28 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [169.229.70.167] (HELO rescomp.berkeley.edu) (169.229.70.167) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2006 16:39:28 -0700 Received: by rescomp.berkeley.edu (Postfix, from userid 1007) id EC05F5B766; Wed, 9 Aug 2006 16:39:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rescomp.berkeley.edu (Postfix) with ESMTP id DCE627F403 for ; Wed, 9 Aug 2006 16:39:07 -0700 (PDT) Date: Wed, 9 Aug 2006 16:39:07 -0700 (PDT) From: Chris Hostetter To: java-dev@lucene.apache.org Subject: Re: Why is FuzzyQuery a final class? In-Reply-To: <56a526780608090048t1d5afabbje2549d68796364c@mail.gmail.com> Message-ID: References: <56a526780608090048t1d5afabbje2549d68796364c@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N : forms with a fuzzy term, otherwise I get to much noise). However, FuzzyQuery : is a final class and I cannot extend it. Could that be changed? It's been final since the first rev ... i seem to recall some discussion about many Lucene classes being final as a speed optimization in really old JVMs, so it probably could be changed, but it would be a good idea to audit the variables/methods in the class to make sure they would play nice with subclasses (ie: no private methods that a subclass would likely need to call, etc...) that's not to say however that there isn't still a legitimate reason why the class is final that i'm not realizing. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org