Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of dmsmith555@gmail.com
 designates 209.85.200.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=rGynNcwOVsjPcdnNE9T2KUVQLq+gqZfEIaPjmlNtDvA9fsV9S9Z2Uw96nFmOxAgY1+
         n7i7nNdpxedtl9U+TqttOurgKhboIN37WUFMF/SvmFujgecBxt3LmfqIDrFeMRtySb+e
         ovypMTTiQkoXQK5TQs3Gwm2b1iyY21jft31tI=
Message-ID: <487DFB39.5000909@gmail.com>
Date: Wed, 16 Jul 2008 09:44:25 -0400
From: DM Smith <dmsmith555@gmail.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: java-dev@lucene.apache.org
Subject: TokenStream problem?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

According to the documentation for TokenStream, derived classes are to 
override either next() or next(Token).

Currently, if next(Token) is overridden, but next() is called, payload 
is cloned if it exists in the new token.

However, if next(Token) is called, it is up to the implementation to 
properly maintain payload. It seems to me that since next(Token) is 
called with a new Token(), that this should not be necessary.

Also, if next() is overridden, but next(Token) is called, then payload 
is never cloned, unless the overriding method handles it.

Can someone explain to me why this is correct?

-- DM


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org