W
Wouter
Hi all,
I'm creating a DLL which contains a certain class ( class A), but i forgot
to export it. I created instances from this class in the DLL and passed a
pointers to the executable. I then called some VIRTUAL operations on the
instances. No problem so far. Everything compiled and linked flawless. I
used static linking so the class was also declared in the executable's
project.
I then created some extra non-virtual functionality for class A and wanted
to call these functions too. Now my linker started to complain about
unresolved externals. A quick glance at the header made clear that I forgot
to export the class. I corrected this and again no further problems.
(Visual Studio 6.0)
This made me starting to wonder why the executable did get linked in the
first case where I only called the virtual functions. I would have thought
the linker should also have been complaining. Or am I wrong ?
Can anybody explain this ?
thanks,
Wouter
I'm creating a DLL which contains a certain class ( class A), but i forgot
to export it. I created instances from this class in the DLL and passed a
pointers to the executable. I then called some VIRTUAL operations on the
instances. No problem so far. Everything compiled and linked flawless. I
used static linking so the class was also declared in the executable's
project.
I then created some extra non-virtual functionality for class A and wanted
to call these functions too. Now my linker started to complain about
unresolved externals. A quick glance at the header made clear that I forgot
to export the class. I corrected this and again no further problems.
(Visual Studio 6.0)
This made me starting to wonder why the executable did get linked in the
first case where I only called the virtual functions. I would have thought
the linker should also have been complaining. Or am I wrong ?
Can anybody explain this ?
thanks,
Wouter