[
https://issues.apache.org/jira/browse/LUCENENET-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711208#action_12711208
]
Digy commented on LUCENENET-182:
--------------------------------
Hi Neal,
IndexSearcher#getIndexReader --> IndexSearcher#GetIndexReader
IndexSearcher#close --> IndexSearcher#Close
QueryParser#parse --> QueryParser#Parse
etc.
these kind of changes are already made throughout the Lucene.Net.
So, I can't see any reason why we shouldn't change
StringIndex#loopup to StringIndex#Loopup
and
StringIndex#order to StringIndex#Order
{color:red}
*http://incubator.apache.org/lucene.net/*
Lucene.Net sticks to the APIs and classes used in the original Java
implementation of Lucene. The API names as well as class names are preserved
with the intention of giving Lucene.Net the look and feel of the C# language
and the .NET Framework. For example, the method Hits.length() in the Java
implementation now reads Hits.Length() in the C# port.
{color}
DIGY
> Public fields of StringIndex class should have C# like names
> ------------------------------------------------------------
>
> Key: LUCENENET-182
> URL: https://issues.apache.org/jira/browse/LUCENENET-182
> Project: Lucene.Net
> Issue Type: Improvement
> Environment: Lucene.Net 2.3.2
> Reporter: Digy
> Priority: Trivial
> Attachments: LUCENENET-182.patch, LUCENENET-182.patch
>
>
> Public fields (lookup, order) of Lucene.Net.Search.StringIndex can be/are
> used outside of Lucene.Net and their names should be compatible with C#.
> DIGY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
