About the development of Lucene and the direction of multi-language implementation

On the development of Lucene and the direction of multi-language implementation the development of multi-language Lucene is undoubtedly based on Java Lucene. All of the functional characteristics and compatibility of the problem should be based on Java Lucene. Java Lucene is the originator of the development of Lucene in other languages. So what should be done with the development of multi-language Lucene? Look at the following text:
There is a concerted effort to develop a SWIG Lucene and There are also a clucene and an active LUCENE4C project. I am crazy enough to contemplate a native Ruby port Once upon a time and developed some low-level I/O code and then real ized What a maintenance hassle it ' d to keep up with the Always evolving Java lucene.the Pylucene-Crew (credit where its Due, Andi vajda!) Did something quite amazing ... using GCJ and SWIG to interface the Java Lucene with Python. This, in my opinion, are the way to future "ports" to any language. Let Java Lucene is the base and all other ports derive from it. I ' m not sure why motivates Garrett with Lucene4c-and I certainly does not want to discourage anyone from tackling this as At the very least it are a great computer science exercise and surely a learning experience for anyone it. If you are continue with your port, you are are going to have to face the realization this you'll always be behind the Java vers Ion in terms of features and compatibility-Unless you ' re able to implement the features every time in a commit message.> for example, I know that Portersteim Mer is deprecated by snowball ... > exist> other classes not worth to port now? If you don ' t have spending every waking moment porting, why not join forces with the SWIG Lucene folks and interface to Which from delphi?> something else I must know? The code is based in Lucene 1.4.3...You ' re already behind and there has been dramatic changes with the latest codebase tha T would be Lucene 1.9/2.0. The author is: Erik, the author of the Lucene in action. The author's main point is: 1, it is best to use similar pylucene way to achieve Lucene's multi-language. 2. The Lucene 1.9/2.0 will be changed greatly. (I'm translating), multilingual lucenene are either difficult to keep compatible with Java Lucene in time, or the process of migrating to multiple languages is hard. Each commit, you need to track, and then modify ... Related connections: Discussion area SWIG profile Google search history