[
https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645787#action_12645787
]
Uwe Schindler commented on LUCENE-1439:
---------------------------------------
In my opinion, these are things that are really not nice currently. The next
major version of Lucene should really fix these annoying inconsistencies
(especially for beginners).
I would be happy to help cleaning the API through 2.9 / 3.0 after some
discussion about this!
> Inconsistent API
> -----------------
>
> Key: LUCENE-1439
> URL: https://issues.apache.org/jira/browse/LUCENE-1439
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 3.0
> Environment: any
> Reporter: Ivan.S
> Priority: Minor
>
> The API of Lucene is totally inconsistent:
> 1)
> There are a lot of containers which don't implement an interface which
> indicates this fact
> (for pre-java-1.5 Lucene it could be Collection, for post-ajva-1.5 Lucene it
> could be more general Iterable)
> Example:
> IndexSearcher: "int maxDoc()" and "doc(int i)"
> 2)
> There are a lot of classes having non-final public accessible fields.
> 3)
> Some methods which return values are named something() others are named
> getSomething()
> Best one is: Fieldable:
> without get: String stringValue(), Reader readerValue(), byte[]
> binaryValue(), ...
> with get: byte[] getBinaryValue(), int getBinaryLength(), ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
