Not completing a using block

[Paulustrious]

Is there any difference in resource usage (or rather disposal between)

using (something resource intensive)
{
DoSomething()
}
return

....and....

using (something resource intensive)
{
DoSomething()
return
}

--
Paul

[Jon Skeet [C# MVP]]

<=?Utf-8?B?UGF1bHVzdHJpb3Vz?= <msdn_whoisat_paulcotter.com>> wrote:

Is there any difference in resource usage (or rather disposal between)

using (something resource intensive)
{
DoSomething()
}
return

...and....

using (something resource intensive)
{
DoSomething()
return
}

Well, if the return statement needs to evaluate anything, the order of
disposal and evaluation will change. In both cases Dispose is called
though.

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

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,


"Paulustrious" <msdn_whoisat_paulcotter.com> wrote in message
news:79**********************************@microsof t.com...

Is there any difference in resource usage (or rather disposal between)

using (something resource intensive)
{
DoSomething()
}
return

...and....

using (something resource intensive)
{
DoSomething()
return
}

Nop, personally I prefer the first one.

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation