I agree with DIGY as well. If, as you say, the HitIterator is "not intended to provide a .NET IEnumerator behavior" than the IEnumerator interface must be removed. That it does not operate according to the IEnumerator documentation is a fatal flaw, and will cause the application developer to experience unexpected and hard to diagnose failures.
This invalid implementation of IEnumerator is sufficient cause for my organization to prohibit use of Lucene.Net in any development project. -- Neal -----Original Message----- From: George Aroush (JIRA) [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 29, 2007 8:41 PM To: [email protected] Subject: [jira] Closed: (LUCENENET-97) HitIterator does not correctly implement System.Collections.IEnumerator [ https://issues.apache.org/jira/browse/LUCENENET-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Aroush closed LUCENENET-97. ---------------------------------- Resolution: Invalid I agree with DIGY. One of the goals of Lucene.Net is to keep it consistent with Lucene Java. The behavior of HitIterator is not intended to provide a .NET IEnumerator behavior, but, like DIGY said, an efficient iteration over Lucene hits. The current behavior of HitItterator is consistent with the Lucene Java; this behavior must remain (and the efficiency). Btw, another Apache project, NMaven (a port from Java to C#) has the following question: "There is some concern that NMaven may be drifting from Maven in terms of common architecture/code". Lucene.Net should not drift. I'm closing this issue. Further discussion about it should move to the mailing list. Regards, -- George > HitIterator does not correctly implement System.Collections.IEnumerator > ----------------------------------------------------------------------- > > Key: LUCENENET-97 > URL: https://issues.apache.org/jira/browse/LUCENENET-97 > Project: Lucene.Net > Issue Type: Bug > Environment: .NET > Reporter: Neal Granroth > > method MoveNext() is supposed to increment the position within the list; it > does not. > method Current() is supposed to return the object at the current position, > but not change the position within the list. > It incorrectly moves to the next position. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
