I think a non-static would be cleaner in this case, but people would have to be more careful. Isn't it true that the old (1.4) boolean scorer can deliver docs in non-index order? That means you can't use it as a component of anything that requires in-order docs (the new scorer, or Paul's proposed FilteredQuery that uses skipTo).
Other options: - expose the old scorer as a different query... class BooleanQuery14 extends BooleanQuery (same compatibility drawbacks as above though) - don't expose the old scorer at all (or make access protected or package-protected) -Yonik Now hiring -- http://forms.cnet.com/slink?231706 > > The actual problem is that this flag in BooleanQuery is static, so an > > even better solution would be to make it a normal attribute of each > > BooleanQuery object. > > I agree. Statics are often more trouble than they're worth. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
