I go back and forth on this one. On one hand, people using VB.NET can't use lucene.net because of this blocking issue. On the other, it's possible people have production code (think even Stackoverflow) possibly using these fields, and changing them without obsoleting them first could cause a huge headache for them, though I realize they will have to do it at some point anyway.
In most cases, it's a discrepancy between fields and properties. I would hope most people chose to use the property instead of the field. In other cases, it's a public field (that should be been private or protected internal) that has the same name as a method. So I would like more opinions here if possible, though I would rather just push it through. Unfortunately, people have gotten busy with holidays and/or work (understandable), so activity seems to be dwindling. On Sat, Jan 21, 2012 at 12:49 AM, Prescott Nasser <geobmx...@hotmail.com>wrote: > I'd say push it through. This needs to happen so something's will have to > break - there isn't a way around it. Lets just make sure to really document > what we are changing > > Sent from my Windows Phone > ________________________________ > From: Christopher Currens (Commented) (JIRA) > Sent: 1/21/2012 12:33 AM > To: lucene-net-dev@lucene.apache.org > Subject: [Lucene.Net] [jira] [Commented] (LUCENENET-446) Make Lucene.Net > CLS Compliant > > > [ > 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 > > >
