[
https://issues.apache.org/jira/browse/LUCENENET-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775440#action_12775440
]
Nicholas Paldino commented on LUCENENET-202:
--------------------------------------------
It's not that much of a concern. While I agree, all warnings should be
abolished, the concern is to get the current port of Lucene.NET to match the
functionality of the current version of Lucene. It's been discuessed that when
they move to .NET 3.5, they are going to branch off, and use .NET code
constructs, best practices, etc, etc.
I will strongly suggest that this issue be addressed then, forcing "treat
warnings as errors" to be introduced into the project.
> Compile warnings trying to build source code, svn revision 829945
> -----------------------------------------------------------------
>
> Key: LUCENENET-202
> URL: https://issues.apache.org/jira/browse/LUCENENET-202
> Project: Lucene.Net
> Issue Type: Bug
> Environment: VS C# Express 2008. A
> Reporter: Corey Trager
>
> C:\cit\lucene\C#\src\Lucene.Net\Search\ComplexExplanation.cs(69,12): warning
> CS0472: The result of the expression is always 'true' since a value of type
> 'bool' is never equal to 'null' of type 'bool?'
> C:\cit\lucene\C#\src\Lucene.Net\Search\ComplexExplanation.cs(69,24): warning
> CS0429: Unreachable expression code detected
> C:\cit\lucene\C#\src\Lucene.Net\Index\FormatPostingsDocsWriter.cs(42,17):
> warning CS0649: Field 'Lucene.Net.Index.FormatPostingsDocsWriter.freqStart'
> is never assigned to, and will always have its default value 0
> C:\cit\lucene\C#\src\Lucene.Net\Analysis\Standard\StandardTokenizerImpl.cs(230,15):
> warning CS0414: The field
> 'Lucene.Net.Analysis.Standard.StandardTokenizerImpl.yycolumn' is assigned but
> its value is never used
> C:\cit\lucene\C#\src\Lucene.Net\Analysis\Standard\StandardTokenizerImpl.cs(233,16):
> warning CS0414: The field
> 'Lucene.Net.Analysis.Standard.StandardTokenizerImpl.zzAtBOL' is assigned but
> its value is never used
> C:\cit\lucene\C#\src\Lucene.Net\Index\DocFieldProcessorPerThread.cs(42,18):
> warning CS0649: Field 'Lucene.Net.Index.DocFieldProcessorPerThread.docBoost'
> is never assigned to, and will always have its default value 0
> C:\cit\lucene\C#\src\Lucene.Net\Index\CharBlockPool.cs(31,16): warning
> CS0649: Field 'Lucene.Net.Index.CharBlockPool.numBuffer' is never assigned
> to, and will always have its default value 0
> C:\cit\lucene\C#\src\Lucene.Net\Store\NIOFSDirectory.cs(87,35): warning
> CS0649: Field 'Lucene.Net.Store.NIOFSDirectory.NIOFSIndexInput.byteBuf' is
> never assigned to, and will always have its default value null
> C:\cit\lucene\C#\src\Lucene.Net\Store\NIOFSDirectory.cs(90,35): warning
> CS0649: Field 'Lucene.Net.Store.NIOFSDirectory.NIOFSIndexInput.otherByteBuf'
> is never assigned to, and will always have its default value null
> C:\cit\lucene\C#\src\Lucene.Net\Analysis\CharReader.cs(32,35): warning
> CS0649: Field 'Lucene.Net.Analysis.CharReader.input' is never assigned to,
> and will always have its default value null
> C:\cit\lucene\C#\src\Lucene.Net\Index\DocumentsWriter.cs(181,37): warning
> CS0649: Field 'Lucene.Net.Index.DocumentsWriter.newFiles' is never assigned
> to, and will always have its default value null
> C:\cit\lucene\C#\src\Lucene.Net\Index\TermVectorsTermsWriter.cs(35,30):
> warning CS0649: Field
> 'Lucene.Net.Index.TermVectorsTermsWriter.termVectorsWriter' is never assigned
> to, and will always have its default value null
> C:\cit\lucene\C#\src\Lucene.Net\Index\TermsHash.cs(43,21): warning CS0169:
> The field 'Lucene.Net.Index.TermsHash.primaryTermsHash' is never used
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
