[
https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan.S reopened LUCENE-1439:
----------------------------
No one seems to care about this issue since it is closed, so I dare to reopen
it (after I created a Wiki page as proposed by others).
Please, everyone who knows inconsistencies in Lucene API (there seems to be
plenty of)
please report to Wiki page:
http://wiki.apache.org/jakarta-lucene/MakingApiConsistent
Thank you.
> 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]
