[ 
https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645826#action_12645826
 ] 

Ivan.S commented on LUCENE-1439:
--------------------------------

I was thinking about this issue as a "request". Sadly, I currently don't have 
time to crawl through an unknown API and search for all inconsistencies.
The comments imply, that other people know what I'm talking about. So perhaps, 
instead of closing the issue as 'incomplete', someone (who already KNOWS this 
API) could list most frequent 'inconsistent' classes?
The fact that I'm new to Lucene makes it very probable that my proposed patches 
will be rejected anyway (because they would just "not fit" somehow).
Second thing is: I read few comments about java-1.5-only vs not-java-1.5-only 
policy for future Lucene. It seems that even the developers can't agree on this 
issue. How could I?

> 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]

Reply via email to