Set variable=null ?

[stuartd]

Hi,

I know that c# has automatic garbage collection, but i have seen some code like this:

object o = new object;
...
{code to use object}
...
o=null;

Is the "o=null;" required or recommended?

SD

 

[JurkMonkey]

This really shouldn't be done for the purpose of garbage collection. Let C# do it for you.

 

[stuartd]

Do you know what the purpose of that line is?

SD

 

[cappmgr]

Though there is nothing wrong with setting an object in memory to null when you are no longer going to use it. If it is huge it may make a difference.
Marty

 

[NeilTrain]

Its useful when the variable will no longer be used, but the scope its in (method, etc) won't end (fire garbage collection) soon. Say you have this huge object that hogs up resources, and you are done using it, but still have a lot more code to run in that method. Then it could be benificial to set it to null.

 

[chiph]

Say you have this huge object that hogs up resources

Then the object should implement IDisposable, and the caller should call .Dispose() on it when it's done using it (or surround it with a using block)

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first

 

[NeilTrain]

Chip,
Does using the Dispose() or the using block have a benifit over just setting it to null? Or is it just better practice.

 

[chiph]

It's better practice, as the framework "knows" about IDisposable.

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first