On Tue, Aug 18, 2009 at 8:01 PM, Michael Busch<busch...@gmail.com> wrote: > On 8/14/09 9:23 AM, Yonik Seeley wrote: >> Another thing I was wondering about was the opacity of State - one >> can't inspect or change the attributes w/o restoring it first. >> Undesirable limitation, or feature allowing more flexible state >> implementations? >> > > Excellent point! This limitation is currently there to discourage changing > values of > a state, because that would be rather inefficient: you'd have to lookup the > attribute(s) > of each state you want to change.
Yeah, but restoring state also involves looking up attributes... so if one is going to skip around a cached list of States (tokens), it can still be more efficient to not restore each. -Yonik http://www.lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
