Home/ Questions/Q 848915
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T07:01:05+00:00

Is it bad idea to have static CComPtr member variables in an application. Since

  • 0

Is it bad idea to have static CComPtr member variables in an application.
Since we cannt control destruction of static variable and it can happen after CoUninitialze .

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Provided you take the appropriate precautions, then using a CComPtr as a static member is not inherently evil.

    By “appropriate precautions”, I mean you should consider:

    • Mutexing access to it;
    • Ensuring that it has been initialised
      before usage;
    • Maintining a mutexed, static instance count for your own class;
    • Ensuring that CComPtr::Release is called in your class’ own FinalRelease method when the instance count reaches zero.
    • 0