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.
- RE: at least one doc Nicholas Paldino [.NET/C# MVP]
- RE: at least one doc Digy
- RE: at least one doc Nicholas Paldino [.NET/C# MVP]
- RE: at least one doc Granroth, Neal V.
- RE: at least one doc Nicholas Paldino [.NET/C# MVP]
- RE: at least one ... Digy
- RE: at least one ... Nicholas Paldino [.NET/C# MVP]
- RE: at least one ... Franklin Simmons
- RE: at least one ... Michael Garski
- RE: Performance o... Nicholas Paldino [.NET/C# MVP]
- Re: at least one ... Ben Martz
- RE: at least one ... Michael Garski
- Re: at least one ... Ben Martz
- Re: at least one doc Ciaran Roarty
- RE: at least one doc Todd Carrico
- RE: at least one doc Nicholas Paldino [.NET/C# MVP]
- RE: at least one doc Franklin Simmons
- Re: at least one doc Todd Carrico
