Re: ATL Asserts

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Tue, 5 Jun 2007 16:30:35 -0400

Message-ID:

<ejGfgB7pHHA.3888@TK2MSFTNGP05.phx.gbl>

Kim Gr?sman <kim@mvps.org> wrote:

hangaround <hangaround@discussions.microsoft.com> wrote:

In my application related to ATL , the compiler always asserts me
with m_bInitialized); and I trace the codess find that

You are creating a CComObject-based class with new, like this:

CComObject<MyClass>* p = CComObject<MyClass>();

Should there be a call to operator new in there?

Quite. Sorry for the typo. I meant

CComObject<MyClass>* p = new CComObject<MyClass>();

It's cool that that's enforced now, though, thinking about it,
shouldn't CComObject<T>'s constructor be private?

Then you would have to make CComCreator and CComInternalCreator friends
of CComObject. And what if I want to plug in my own creator class (not
that I've ever felt the need)?
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925