lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Nicholson <>
Subject CLS Compliance and Compiler Warnings
Date Tue, 13 Oct 2009 15:24:19 GMT
I apologize if this has been asked already, but is there any effort underway
or interest in getting Lucene.NET to compile as a CLS-Compliant assembly?
What about reducing or eliminating the compiler warnings? I know both of
these would make my build environment a little saner.  Looking at the code
it looks like there is not much involved in getting it to compile clean.  I
noticed a few things in particular:

* unused variables - warning
* protected internal fields with different case than a public property or
class - non-cls compliant
* public consts that start with underscore - non-cls compliant

Is there some reason the code needs to stay exactly the way it is (like
maintaining parity with the Java project)?  It seems like a pretty small
amount of work, I'd be happy to submit a patch if anyone thinks it would be

Best Regards,
Eric Nicholson

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