Re: dynamic_cast does not work across modules with multiple inheritance (VC2005)
On 7 Jul 2006 07:34:34 -0700, "kaislavirta@gmail.com"
<kaislavirta@gmail.com> wrote:
I have a project which has been running well on VC6 for years now, but
now more and more reasons are telling me it's time to upgrade. The
system consists of a largish number of dynamically loaded DLLs which
are accessed in some kind of COM fashion.
I have now ported a core set of these but run into a big problem: RTTI
does not work correctly (=the way I want it to) between DLLs anymore,
which it did in VC6.
My setup is this:
class IBase
{
public:
virtual Foo() = 0;
};
class IDerivedOne : virtual public IBase
{
public:
virtual Bar() = 0;
};
class IDerivedTwo : virtual public IBase
{
public:
virtual Goo() = 0;
};
class Test : public IDerivedOne, public IDerivedTwo
{
public:
Foo();
Bar();
Goo();
};
What I then do is load a module (could be the same executable) where
Test is implemented, get a pointer to a new instance of the object (as
an IBase*) through a class factory and then do a dynamic_cast to
IDerivedOne*. However, the dynamic_cast returns NULL and I can't get it
to understand what I want.
Is this the way it should be or should it give me the pointer I want?
reinterpret_cast does not work either, as a cast to IDerivedOne would
really give me IBase disguised as IDerivedOne, to disastrous results.
Does anyone know how to deal with this? Or do you need more code to see
what's going on?
Certainly, you should be able to do that with dynamic_cast. I've not
encountered the problem you've described, but the seams between modules
(EXE and DLL) are very apparent under the Windows model of dynamic linking,
and this could be a new manifestation of that. Assuming you recompiled
everything from scratch with the new compiler, the next thing to check is
that you're really creating a Test object. After that, see if everything is
compiled with /GR, and in general, that all the relevant compiler options
agree between the modules. What about the class "Test"? Is it implemented
in only one module (DLL or EXE)? If it's all inline, does more than one
module create instances of it? If so, see if it helps to create instances
in only one place, and if it can be said to live in a DLL, try decorating
it with __declspec(dllexport|dllimport), using the well-known macro method.
--
Doug Harrison
Visual C++ MVP