I'm fine w/ making this change. No sense in implementing both as we
can just rely on next(Token) to call next(). I will commit the change
and put a comment on the issue that created the SinkTokenizer.
-Grant
On Dec 28, 2007, at 8:43 AM, Doron Cohen wrote:
a TS must implement one of them. I see no harm in implementing
the two (but doing so is likely to just duplicate TokenStream's
code.)
I don't think the contract was ever laid out so strictly. I think
it's fine for any TokenStream to implement both if it's advantageous
to do so.
From TokenStream's Javadocs:
"subclasses must override at least one of next() or next(Token)."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
