Managed C++/CLI

LionAM wrote:

is there any other way to find out if the object
pointed to by pt was destroyed?

Test^ pt;
{
   Test t;
   pt = %t;
}
pt = nullptr;
if (nullptr != pt)
{
   pt->...
}

*edit*  I played around with this and with stack based semantics<br />
the destructor is still called as you stated.  This behavior makes code <br />
like your example dangerous.<br />
<br />
I'd prefer using all reference semantics if I was going to obtain additional<br />
references, something like

Test^ pt;
{
   Test ^t = gcnew Test();
   pt = t;
}
delete pt; // destructor called here!
pt = nullptr;

Mark Salsbery
Microsoft MVP - Visual C++

LionAM wrote:

In my case, I need the local object because it is a lock
(which has to be destroyed when leaving scope).

(from <a href="http://msdn.microsoft.com/en-us/library/ms177197(VS.80).aspx">Destructors and Finalizers in Visual C++</a>[<a href="http://msdn.microsoft.com/en-us/library/ms177197(VS.80).aspx" target="_blank" title="New Window">^</a>]):

Code authored in Visual C++ and compiled with /clr will run a type's destructor for the following reasons:

    * If an object created using stack semantics goes out of scope.
    * If an exception is thrown during the object's construction.
    * If the object is a member in an object whose destructor is running.
    * If you call the delete Operator (C++) on a handle (^ (Handle to Object on Managed Heap)).
    * If you explicitly call the destructor.

If your type is being consumed by a client authored in another language, the destructor will be called when:

    * A call to Dispose.
    * Calling Dispose(void) on the type.
    * If the type goes out of scope in a C# using statement.

Mark Salsbery
Microsoft MVP - Visual C++

suefyzah wrote:

C:\DX90SDK\Samples\C++\DirectShow\BaseClasses\ctutil.h

Mark Salsbery
Microsoft MVP - Visual C++