lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hostetter <hossman_luc...@fucit.org>
Subject Re: [jira] Commented: (LUCENE-623) RAMDirectory.close() should have a comment about not releasing any resources
Date Sun, 09 Jul 2006 06:58:04 GMT

: Just out of curiousity, does Lucene hold onto a RAMDirectory instance
: somewhere after it has called close on it?  If so, that would have been
: the ideal place to fix it any kind of "leak".

Not that I'm aware of.  In my opinion there was no leak, i was just trying
to make RAMDirectory.close() do it's best to release the resources it was
holding on to.

: This patch, while not doing much harm, is not really "best practice" in
: Java and the existing RAMDirectory close() was correct.

Why is this not a best practice?  (or do you mean that in a "not
particularly good" sense instead of "bad" sense?)



-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message