Object Destruction in Managed C++ code

[Craig Whatley]

Is it true that for a managed Visual C++ object, you can write a destructor
and call that destructor to deallocate that object's memory (just like with
an unmanaged C++ object)?

If this is true, will the Garbage Collector free the object when it runs if
you didn't explicitly free the object yourself?

I've read that Visual C++ is the only .NET language that gives the
programmer control over object lifetimes - C#, J#, and Visual Basic have no
choice but to use the garbage collector. Just wanted to make sure this
statement applies to managed C++ objects (like it does to unmanaged C++
objects).

Thanks!
Craig

[Hasani \(remove nospam from address\)]

http://mtaulty.com/blog/archive/2004/06/24/499.aspx

"Craig Whatley" <cr***@aaronmed.com> wrote in message
news:uV**************@TK2MSFTNGP09.phx.gbl...

Is it true that for a managed Visual C++ object, you can write a destructor and call that destructor to deallocate that object's memory (just like with an unmanaged C++ object)?

If this is true, will the Garbage Collector free the object when it runs if you didn't explicitly free the object yourself?

I've read that Visual C++ is the only .NET language that gives the
programmer control over object lifetimes - C#, J#, and Visual Basic have no choice but to use the garbage collector. Just wanted to make sure this
statement applies to managed C++ objects (like it does to unmanaged C++
objects).

Thanks!
Craig

[Craig Whatley]

Good information in that posting - thanks!

"Hasani (remove nospam from address)" <hb********@n0sp4m.popstick.com> wrote
in message news:ut**************@TK2MSFTNGP10.phx.gbl...

http://mtaulty.com/blog/archive/2004/06/24/499.aspx

"Craig Whatley" <cr***@aaronmed.com> wrote in message
news:uV**************@TK2MSFTNGP09.phx.gbl...

Is it true that for a managed Visual C++ object, you can write a

destructor

and call that destructor to deallocate that object's memory (just like

with

an unmanaged C++ object)?

If this is true, will the Garbage Collector free the object when it runs

if

you didn't explicitly free the object yourself?

I've read that Visual C++ is the only .NET language that gives the
programmer control over object lifetimes - C#, J#, and Visual Basic have

no

choice but to use the garbage collector. Just wanted to make sure this
statement applies to managed C++ objects (like it does to unmanaged C++
objects).

Thanks!
Craig