On Mar 3, 2005, at 1:32 PM, Doug Cutting wrote:
Daniel Naber wrote:On Wednesday 02 March 2005 12:25, Erik Hatcher wrote:I'd vote for fixing this as long as the current QueryParser is still available in Lucene core, maybe as OldQueryParser or NoPrecedenceQueryParser. It's surely better to fix it for 2.0 than for 2.x.I agree that the current behavior is awkward. Is it worth breaking backwards compatibility to correct this with the patch applied?
+1. Fixing operator precedence seems to me like an acceptable incompatibility. The change needs to be well documented in release notes, and the old QueryParser should be available, deprecated, for a time for back-compatibility.
Ok, since I'm now deep into JavaCC for a consulting project, I will attempt this change at some point in the near future. It's actually not too hard. If someone wants to beat me to it feel free.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
