You're quite correct to call this out. I'm still not thinking in 2.9 terms yet since by policy I can't use pre-release versions in my software and should have reserved my comments.
On Thu, Jan 14, 2010 at 3:56 PM, Michael Garski <[email protected]>wrote: > Versions prior to 2.3 had it in a few places (most notable > StandardAnalyzer) but in subsequent versions I am not aware of such flow > control other than in QueryParser. What specifically are you referring > to? > > Michael > > -----Original Message----- > From: Ben Martz [mailto:[email protected]] > Sent: Thursday, January 14, 2010 3:54 PM > To: [email protected] > Subject: Re: at least one doc > > The use of exceptions for general code flow control is unfortunately > prevalent in the Lucene java code base and not something that we can > easily > get away from. I've toyed with the idea of creating a comprehensive > "optimized" exception-fee Lucene.Net build just to instrument the > overall > performance difference but I've never had enough free time to give it a > go. > Even if anyone were to complete said build it would be of no use to the > core > Lucene.Net project since it would require changes to quite a number of > methods to return useful status values and would require updating with > every > new release of Lucene.Net. > > -- 13:37 - Someone stole the precinct toilet. The cops have nothing to go on. 14:37 - Officers dispatched to a daycare where a three-year-old was resisting a rest. 21:11 - Hole found in nudist camp wall. Officers are looking into it.
