C#

<br />
public class Something<br />
{<br />
  ...<br />
  public void SomeMethod()<br />
  {<br />
    SomeObj o = new SomeObj();<br />
    o.DoSomeWork();<br />
    // o = null;    << If I don't have this line "o" would stil lbe garbage collected on method exit right?<br />
    return;<br />
  }<br />
  ...<br />
}<br />

devvvy wrote:

If I don't have this line "o" would stil lbe garbage collected on method exit right?

Luc Pattyn wrote:

if o were the only reference to your SomeObj, then setting it null, removes the last reference to the object, and hence makes it collectable

N a v a n e e t h wrote:

setting null will not make any difference for garbage collection

Luc Pattyn wrote:

The GC is *not* analyzing your code to predict whether an object will still be used in the future, it only determines "reachability", i.e. the theoretical possibility to access it again

Luc Pattyn wrote:

In the meantime I have developed a little app that demonstrates exactly how the GC works. When I find
the time, I will write a short article on the subject.

N a v a n e e t h wrote:

So do you usually set null ...

Bitmap b = new Bitmap(filepath);

for(int i = 0; i < b.Width; i++)//Columns
{
   for(int j = 0; j < b.Height; j++)//Rows
   {
     Color c = b.GetPixel(i, j);
     //or do what ever you want with the pixel
   }
}