"Wouter" <wmoors@jtag.nl> wrote in message
news:c1gj4r$ssv$1@reader10.wxs.nl...[color=blue]
> 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[/color]
wanted[color=blue]
> to call these functions too. Now my linker started to complain about
> unresolved externals. A quick glance at the header made clear that I[/color]
forgot[color=blue]
> 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 ?[/color]
Linkers and their behavior are not topical here. Each one will work
in its own way, also necessarily dependent upon the environment in which
it is used.
This newsgroup is about the platform-independent C++ programming language.
See:
http://www.slack.net/~shiva/welcome.txt
For help with your linker, consult support resources available from its
vendor, e.g. websites, tech support, etc. There are probably also one
or more newsgroups which discuss it. Check
www.groups.google.com
or
www.usenet.org etc, to find them.
-Mike
