constructor / destructur

[Thomas]

I'm new in csharp.
I create a SortedList with new objects.
I don't use this SortedList and their objects any more.

Have I to set all objects in the destructor to null?
Or do it the .Net framework for me?

Thanks Thomas

[Bruce Wood]

..NET uses a mark-and-sweep garbage collector. There are rare cases in
which you do need to manually dispose of things, but they are few and
far between.

After the variable that contains the reference to your SortedList goes
out of scope, the garbage collector will automatically clean it up.

[Uchiha Jax]

Out of interest what exactly should you, and should you not, dispose of?
Is it always a good idea to call Dispose on anything that implements
IDisposable or are the rules more lenient?

"Bruce Wood" <br*******@canada.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

.NET uses a mark-and-sweep garbage collector. There are rare cases in
which you do need to manually dispose of things, but they are few and
far between.

After the variable that contains the reference to your SortedList goes
out of scope, the garbage collector will automatically clean it up.

[thomas]

thanks thomas

"Uchiha Jax" <i_************************@NOSPAMhotmail.com> schrieb im
Newsbeitrag news:4n***************@newsfe3-win.ntli.net...

Out of interest what exactly should you, and should you not, dispose of?
Is it always a good idea to call Dispose on anything that implements
IDisposable or are the rules more lenient?

"Bruce Wood" <br*******@canada.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

.NET uses a mark-and-sweep garbage collector. There are rare cases in
which you do need to manually dispose of things, but they are few and
far between.

After the variable that contains the reference to your SortedList goes
out of scope, the garbage collector will automatically clean it up.

[Jon Skeet [C# MVP]]

Uchiha Jax <i_************************@NOSPAMhotmail.com> wrote:

Out of interest what exactly should you, and should you not, dispose of?
Is it always a good idea to call Dispose on anything that implements
IDisposable or are the rules more lenient?

I believe it's a good idea to call Dispose on anything that implements
IDisposable if your code is the owner of it (and unfortunately that's
sometimes not clear).

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Champika Nirosh]

not always...

The using statement disposes of the resource

A using statement of the form

using (R r1 = new R()) {
r1.F();
}

is precisely equivalent to

R r1 = new R();
try {
r1.F();
}
finally {
if (r1 != null) ((IDisposable)r1).Dispose();
}

Regards,
Nirosh.

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message news:MP************************@msnews.microsoft.c om...

Uchiha Jax <i_************************@NOSPAMhotmail.com> wrote:

Out of interest what exactly should you, and should you not, dispose of?
Is it always a good idea to call Dispose on anything that implements
IDisposable or are the rules more lenient?

I believe it's a good idea to call Dispose on anything that implements
IDisposable if your code is the owner of it (and unfortunately that's
sometimes not clear).

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Champika Nirosh <te**@test.lk> wrote:

not always...

The using statement disposes of the resource

A using statement of the form

using (R r1 = new R()) {
r1.F();
}

is precisely equivalent to

R r1 = new R();
try {
r1.F();
}
finally {
if (r1 != null) ((IDisposable)r1).Dispose();
}

I'm not sure what your point is. Yes, the using statement is the
easiest way to call Dispose, but that's still calling Dispose...

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Champika Nirosh]

My initial thought was that u implied to call Dispose manually.. and second
is "using" statement is not always call Dispose, if a null resource is
acquired, then no call is made to Dispose. Anyway I think your statement
covers this seemlessly

Regards,
Nirosh.

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

Champika Nirosh <te**@test.lk> wrote:

not always...

The using statement disposes of the resource

A using statement of the form

using (R r1 = new R()) {
r1.F();
}

is precisely equivalent to

R r1 = new R();
try {
r1.F();
}
finally {
if (r1 != null) ((IDisposable)r1).Dispose();
}

I'm not sure what your point is. Yes, the using statement is the
easiest way to call Dispose, but that's still calling Dispose...

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Champika Nirosh]

My initial thought was that u implied to call Dispose manually.. and second
is "using" statement is not always call Dispose, if a null resource is
acquired, then no call is made to Dispose. Anyway I think your statement
covers this seemlessly

Regards,
Nirosh.

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

Champika Nirosh <te**@test.lk> wrote:

not always...

The using statement disposes of the resource

A using statement of the form

using (R r1 = new R()) {
r1.F();
}

is precisely equivalent to

R r1 = new R();
try {
r1.F();
}
finally {
if (r1 != null) ((IDisposable)r1).Dispose();
}

I'm not sure what your point is. Yes, the using statement is the
easiest way to call Dispose, but that's still calling Dispose...

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too