Re: Share .cpp and .h along projects
- From: "Doug Harrison [MVP]" <dsh@xxxxxxxx>
- Date: Mon, 13 Aug 2007 14:50:02 -0500
On Mon, 13 Aug 2007 12:12:51 -0700, "Alexander Nickolov"
<agnickolov@xxxxxxxx> wrote:
COM is for binary compatibility. DLLs are binary objects
and it fits with them naturally. C++ classes are _not_ binary
entities and thus should _never_ be exported from DLLs -
period. It's a terrible deployment practice eclipising any bad
coding habits you might have! The proper way to export
C++ classes is using a static library. This signifies they are
part of your program, not part of a separate deployment unit.
This use of DLLs is not what you're calling "deployment". If you consider
it to be a poor attempt at COM and not equivalent to static linking, well,
of course you're going to feel that way. That's what I was getting at in my
original message. It is mistaken expectations that cause people to say
things like this. You've mistaken it for something it's not, and anyone who
recognizes it for what it is and uses it correctly and successfully just
doesn't know what they're doing.
--
Doug Harrison
Visual C++ MVP
.
- Follow-Ups:
- Re: Share .cpp and .h along projects
- From: Ben Voigt [C++ MVP]
- Re: Share .cpp and .h along projects
- References:
- Share .cpp and .h along projects
- From: Stefano
- Re: Share .cpp and .h along projects
- From: Ulrich Eckhardt
- Re: Share .cpp and .h along projects
- From: Ben Voigt [C++ MVP]
- Re: Share .cpp and .h along projects
- From: Ulrich Eckhardt
- Re: Share .cpp and .h along projects
- From: Ben Voigt [C++ MVP]
- Re: Share .cpp and .h along projects
- From: Doug Harrison [MVP]
- Re: Share .cpp and .h along projects
- From: Alexander Nickolov
- Share .cpp and .h along projects
- Prev by Date: Re: How come a 20MB file becomes a 50KB Memory object?
- Next by Date: Re: Bit field vs bit manipulation?
- Previous by thread: Re: Share .cpp and .h along projects
- Next by thread: Re: Share .cpp and .h along projects
- Index(es):
Relevant Pages
|