Skip to content

Commit 21bcbe5

Browse files
authored
Update details-about-destructors.md (MicrosoftDocs#5489)
Fix link to IUnknown::Release
1 parent 9d74761 commit 21bcbe5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

uwp/cpp-and-winrt-apis/details-about-destructors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In the [Diagnosing direct allocations](./diag-direct-alloc.md) topic, we mention
2121

2222
The benefit of having a public destructor is that it enables deferred destruction, which is the ability to detect the final [**IUnknown::Release**](/windows/win32/api/unknwn/nf-unknwn-iunknown-release) call on your object, and then to take ownership of that object to defer its destruction indefinitely.
2323

24-
Recall that classic COM objects are intrinsically reference counted; the reference count is managed via the [**IUnknown::AddRef**](/windows/win32/api/unknwn/nf-unknwn-iunknown-addref) and **IUnknown::Release** functions. In a traditional implementation of **Release**, a classic COM object's C++ destructor is invoked once the reference count reaches 0.
24+
Recall that classic COM objects are intrinsically reference counted; the reference count is managed via the [**IUnknown::AddRef**](/windows/win32/api/unknwn/nf-unknwn-iunknown-addref) and [**IUnknown::Release**](/windows/win32/api/unknwn/nf-unknwn-iunknown-release) functions. In a traditional implementation of **Release**, a classic COM object's C++ destructor is invoked once the reference count reaches 0.
2525

2626
```cppwinrt
2727
uint32_t WINRT_CALL Release() noexcept

0 commit comments

Comments
 (0)