🚀 go-pugleaf

"Rudy Velthuis [TeamB]" <velthuis@gmail.com> wrote in message
news:xn0dkx9y9ftcjf013-moderator@newsgroups.borland.com...
> At 21:53:14, 17.07.2004, Lord Crc wrote:
>
> > On Sat, 17 Jul 2004 11:23:16 -0400, "Marc Rohloff [TeamB]" <"on
> > request"> wrote:
> >
> > > It is also incorrect.
> >
> > Why not use "using" ? it's SOOO nice for these type things.
>
> We discussed this before. Using calls IDispose.Dispose(), and not
> Close(). Technically there may be no big difference, but semantically,
> there is. I personally would not rely on the fact that both would do
> exactly the same, since both (or a descendant class) don't *have* to do
> exactly the same.


Sure, Close and Dispose are two different methods, but in the .NET
Framework, Close methods call the Dispose method.  That is the pattern, it
is fairly well known by now, and anyone that doesn't follow the Dispose
pattern properly needs to be educated.  IMO, the benefits of the "using"
statement in code clarity and maintenance far outweigh the small risk of
someone not implementing thier Dispose pattern properly.

Joe
-- 
Joe Mayo, Author/Instructor
Need C#/.NET training?
visit www.mayosoftware.com
C# Tutorial - www.csharp-station.com