C#

George_George wrote:

Implement the dispose design pattern on a base type that commonly has derived types that hold onto resources, even if the base type does not.

class MyBase : IDisposable
{
 protected virtual void Dispose(bool disposing)
    {
        if (!disposed)
        {
            if (disposing) { }
            disposed = true;
        }
    }

    ~MyBase()
    {
        Dispose(false);
    }

    public void Dispose()
    {
        Dispose(true);
        GC.SuppressFinalize(this);
    }
}

class MyDerived : MyBase
{
    protected virtual void Dispose(bool disposing)
    {
        if (!disposed)
        {
            if (disposing) { }
            disposed = true;
        }
         base.Dispose(disposing);
    }
}

George_George wrote:

Does it mean when in the situation of when both base class and derived class wraps native resource, we only need to put Finalize method to the derived class?

George_George wrote:

If my class has a StreamWriter member, and in Finalizer, I do not close it, and I rely on the Finalizer method of StreamWriter itself to close the native resource file handle. In this case, will there be any resource leak?