Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 37915 invoked from network); 24 Jul 2007 22:08:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Jul 2007 22:08:07 -0000 Received: (qmail 14700 invoked by uid 500); 24 Jul 2007 22:08:05 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 14633 invoked by uid 500); 24 Jul 2007 22:08:05 -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 14622 invoked by uid 99); 24 Jul 2007 22:08:05 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jul 2007 15:08:05 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [66.111.4.26] (HELO out2.smtp.messagingengine.com) (66.111.4.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jul 2007 15:08:04 -0700 Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 2001A9E21 for ; Tue, 24 Jul 2007 18:07:43 -0400 (EDT) Received: from web8.messagingengine.com ([10.202.2.217]) by compute1.internal (MEProxy); Tue, 24 Jul 2007 18:07:43 -0400 Received: by web8.messagingengine.com (Postfix, from userid 99) id E8DCCB822; Tue, 24 Jul 2007 18:07:42 -0400 (EDT) Message-Id: <1185314862.32739.1201861589@webmail.messagingengine.com> X-Sasl-Enc: XLAJqp5y/Bc8QKb9L3o0RqXz4D2SqgpUR5rs+gNPVAOb 1185314862 From: "Michael McCandless" To: java-dev@lucene.apache.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface References: Subject: Re: Token termBuffer issues In-Reply-To: Date: Tue, 24 Jul 2007 18:07:42 -0400 X-Virus-Checked: Checked by ClamAV on apache.org "Doron Cohen" wrote: > "Michael McCandless" wrote: > > > boolean next(Token resToken) > > > > which returns true if it has updated resToken with another token, > > else false if end-of-stream was hit. > > I would actually prefer > Token next(Token resToken) > because: > - this was the API with reuse is very much like the one without reuse > (except for the reusable param) - easier for app dev. > - it allows to return useful result also in cases where the specific > implementation does not support reuse, or null was passed (indicating > reuse > is not desired), or something in the data/state inhibited reuse. I see. So the callee is allowed to return a different token than resToken? Ie passing "resToken" is just a suggestion that you may use resToken to return your result but you are not required to. OK I'll try this approach... Mike --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org