[
https://issues.apache.org/jira/browse/LUCENENET-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190349#comment-13190349
]
Christopher Currens commented on LUCENENET-446:
-----------------------------------------------
I've decided to start work on this issue again. I'm not going to go about and
change all of the signed vs unsigned types for so many reasons. I'm going to
focus on just making naming CLS compliant, really just so it can be used in
case-insensitive languages, like VB.
The problem is that may of the variables are public (they are not public in
java, and shouldn't be in .NET), so I really have no way of knowing if they are
being used in external code. We have Obsolete attributes on SOME of them, but
not all. Should we push through this and just make the changes or wait for
another release and mark them obsoleted in the meantime?
> Make Lucene.Net CLS Compliant
> -----------------------------
>
> Key: LUCENENET-446
> URL: https://issues.apache.org/jira/browse/LUCENENET-446
> Project: Lucene.Net
> Issue Type: Task
> Components: Lucene.Net Core
> Affects Versions: Lucene.Net 2.9.4
> Reporter: Prescott Nasser
> Attachments: Lucene2.9.4-CLS-partial-fix
>
>
> Make Lucene.Net CLS Compliant
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
