lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Naber <lucenel...@danielnaber.de>
Subject Re: Analyzer as an Interface?
Date Wed, 20 Jul 2005 21:53:32 GMT
On Tuesday 19 July 2005 22:11, Wolfgang Hoschek wrote:

> Daniel, what's the use case that would make this a significant  
> improvement over extending and overriding the single abstract method?  
> Classes that implement multiple interfaces? 

Yes, exactly.

> thoughts would apply to TokenStream, IndexReader/Writer, etc. Also  
> note that once it's become an interface the API is effectively frozen  
> forever.

Well, not forever, but any change will lead to an incompatible API, that's 
an important point. One could however provide an abstract class 
"AbstractAnalyzer" which implements the interface and which can be 
extended by those who don't need the Lucene analyzer to be an interface. 
Those people wouldn't be affected by changes then (at least not more than 
they are now).

Regards
 Daniel

-- 
http://www.danielnaber.de

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message