Re: Share .cpp and .h along projects
- From: Alex Blekhman <tkfx.REMOVE@xxxxxxxxx>
- Date: Tue, 14 Aug 2007 13:17:48 +0300
Doug Harrison [MVP] wrote:
__declspec(dllexport) is going to break that all the time, in a way that a COM-compatible interface (doesn't have to be COM-compliant with all the extra registry stuff) won't.
You perceive that problem only because of your beliefs concerning DLL
substitutability. If you believed that __declspec(dllexport|dllimport) of
classes is equivalent to static linking WRT compilation dependencies, you
wouldn't think you could just overwrite a DLL with a newer version.
Instead, you'd understand you need to recompile all the DLL's clients.
Actually, Ben has a point here. DLL's have long been boasted of their substitutability and "after-market support", as MSDN puts it. Without these advantages over static libs (who cares about memory or disk savings anymore) DLL's have nothing to offer.
Alex
.
- Follow-Ups:
- Re: Share .cpp and .h along projects
- From: Doug Harrison [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
- Re: Share .cpp and .h along projects
- From: Doug Harrison [MVP]
- Re: Share .cpp and .h along projects
- From: Ben Voigt [C++ MVP]
- Re: Share .cpp and .h along projects
- From: Doug Harrison [MVP]
- Share .cpp and .h along projects
- Prev by Date: Re: array -- foo, &foo and &foo[0]
- Next by Date: Re: seek a method to get a function's input stack address ?
- Previous by thread: Re: Share .cpp and .h along projects
- Next by thread: Re: Share .cpp and .h along projects
- Index(es):
Loading