> In my experience, it's very rare to have members which are unneeded
until the rest of the object becomes eligible for garbage collection.
In fact, I can't remember the last time it made sense to set something
to null just for the sake of garbage collection.
Like I said it depends on application. Local variables allocated on stack -
I agree, there is not much sense in nulling them. However, I would suggest
to check the topic "Set Unneeded Member Variables to Null Before Making
Long-Running Calls" in the link I recommended. It explains some of caveats
with local variables. Problem is that any heap allocation under certain
conditions can survive GC cycles for very long periods of time. Which
finally can cause troubles. That's why I suggest not to adopt generic rules,
which might work or not. Definition of long call is very application
specific.
HTH
Alex