C#

Christian Graus wrote:

You need a Dispose method if you want to offer a way to free memory immediately

Guffa wrote:

Freeing (managed) memory is no reason to implement IDisposable.

Guffa wrote:

The only time that there would be any point in having a Dispose method for removing references, is if you plan to hold on to the object after it's disposed

Guffa wrote:

That sound's a bit creapy, though... like keeping your dead pets in the freezer...

Christian Graus wrote:

I'd say that if a large amount of memory is being used by commonly created objects, Dispose should be implimented to control cleanup.

Christian Graus wrote:

The point is, the Dispose method on the class in question, would be used to manage a resource count, before deciding if it should in fact call Dispose on an object which it contains.

Guffa wrote:

Objects that doesn't own unmanages resources (or objects that implement IDisposable) don't need a Dispose method or a finalizer. You can just remove the reference to your object (or let it go out of scope), and the object will be freed by the garbage collector eventually.

public void F()
{
    Object obj = new Object();
    // Do some stuff with the object
    obj = null;
}

shyagam wrote:

If no finalizer is present, where than should I remove the reference to my object?

Class A {
   private List<string> _list;
   public A() {
      _list = new List<string>();
   }
   public List<string> List { get { return _list; } }
   public Add(string s) {
      _list.Add(s);
   }
}

Also, is the last statement in the following code redundent?
I think of it as a good programming practice, as you can be sure that the reference was removed.

public void F()
{
Object obj = new Object();
// Do some stuff with the object
obj = null;
}

Saira Tanwir wrote:

my DataTable contains the record from a DB table in row and column format.

Saira Tanwir wrote:

i want to access the record value on a specific location in the datatable by specifying the row and column number, and then retrieving the value on that particular locaion.

DataRow row = myTable.Rows[rowIndex];

object value = row[columnIndex];

sharpiesharpie wrote:

Err..i haven't realy tested it but how about....rchTextCode.Text.Undo()?

sharpiesharpie wrote:

of cource it'll delete everything if u tell it to undo the entire textbox and not the text it in...