On Mon, 31 Mar 1997, Christian Hudon wrote: > On Mar 31, Nicolás Lichtmaier wrote > > More programs would share DLL if it wasn't asking for trouble like it is > currently. Just take MFC or OWL as an example... Quite a few progams use > one or the other, both Microsoft and Borland ship them as DLLs, but most > programs either install their own private copy or get linked statically to > avoid all the trouble that mismatching versions, etc. cause when > sharing DLLs (or at least attempting to).
Unless GCC is some all powerfull god like compiler this exact problem exists in Linux too. Any shard code system basically breaks badly when you try and use C++. The problem is quite simply that C++ has no standards for binary class layout and no standard way to specify an order in the class as well as having no way to upgrade base classes without breaking the derived classes. All this means that if the header files of a C++ library are ever changed the interface provided by the shared code will also change. So you end up each and every version of <cpp lib> on your system that has ever been released! This is why MFC and OWL are such pains in windows :< Jason
