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.

Reply via email to