×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Walden H. Leverich wrote:
or even remove references early by setting them to null.
Assuming the JVM GC is roughly as smart as the CLR's GC, setting the
reference to null is an unnecessary step. An object is eligible for
collection when it can no longer be referenced... it doesn't actually
need to be out of scope yet.
In the trivial cases this is true, but I think one has to be careful
when dealing with collections and arrays. The problem of arrays holding
object references when they are no longer accessible via business rules
is well documented. I would guess you could have a similar problem with
collections and maps where you think you no longer have references to
your object, but indeed do. Setting references to null in some of these
non-trivial cases is vital.
Brian
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.