Re: Share .cpp and .h along projects

From:

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam>

Newsgroups:

microsoft.public.vc.language

Date:

Mon, 13 Aug 2007 15:57:26 -0500

Message-ID:

<udepcye3HHA.4712@TK2MSFTNGP04.phx.gbl>

"Doug Harrison [MVP]" <dsh@mvps.org> wrote in message
news:ff61c3tt0otrfivah9ui5kmmjjh8o5lfui@4ax.com...

On Mon, 13 Aug 2007 12:26:43 -0500, "Ben Voigt [C++ MVP]"
<rbv@nospam.nospam> wrote:

It is incredibly fragile, non-standard behavior, that produces postings in
this newsgroup continually. The same behavior can be gotten in a robust,
compiler-independent way using COM-compatible binary interfaces. So why
use
__declspec(dllexport)?

Only __declspec(dllexport|dllimport) allows you to (mostly) use the
classes
as you would write them in normal C++. Using the __declspec should be

You can use COM-compatible v-table interfaces perfectly naturally... you
need a factory function and free function or reference counting instead of
new/delete, but that's all you lose. Add a smart pointer and you're about
as "normal C++" as you can get.

viewed as equivalent to static linking, and then you won't lament the fact
it isn't compiler-independent; after all, it was never intended to be. In
comparison, COM is a huge pain in the neck, and I wouldn't even consider
using it unless there was an actual need to use it.

--
Doug Harrison
Visual C++ MVP