lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prescott Nasser <>
Subject RE: [Lucene.Net] [jira] [Commented] (LUCENENET-446) Make Lucene.Net CLS Compliant
Date Sat, 21 Jan 2012 08:49:25 GMT
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
Subject: [Lucene.Net] [jira] [Commented] (LUCENENET-446) Make Lucene.Net CLS Compliant


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:
>             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:!default.jspa
For more information on JIRA, see:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message