lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Currens (JIRA)" <>
Subject [jira] [Commented] (LUCENENET-467) .NETify the public API where appropriate
Date Thu, 07 Jun 2012 17:06:23 GMT


Christopher Currens commented on LUCENENET-467:

Thanks.  Patch applied in revision 1347715
> .NETify the public API where appropriate
> ----------------------------------------
>                 Key: LUCENENET-467
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Improvement
>          Components: Lucene.Net Contrib, Lucene.Net Core
>    Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 2.9.4g, Lucene.Net
>         Environment: all
>            Reporter: Christopher Currens
>              Labels: refactoring
>             Fix For: Lucene.Net 3.0.3
>         Attachments: Lucenenet-467-create.patch
> Although we haven't abandoned the line-by-line port of Java lucene, there are many idioms
in Java that make little to no sense in a .NET assembly.  The API can change to allow for
a conventional .NET experience, while still maintaining the ability and ease during the porting
process of Java logic.
> * Change Getxxx() and Setxxx() methods to .NET Properties
> * Implement the [dispose pattern|]
properly.  Try, at all costs, to only use finalizers *when necessary*.  They are expensive,
and most of the classes used already have finalizers that will be called.
> * Convert Java Iterator-style classes (see TermEnum, TermDocs and others) to implement
> * When catching exceptions, do not use *throw;* instead of *throw ex;* to maintain the
stack trace

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:


View raw message