That would mean that I can't ever link any of my programs which uses the STL against any library not built by myself using the same compiler because I can't ever be sure that it uses the STL, too and may be built with another version of VS.
I wonder how the STL ever could get adapted by programmers under these preconditions.
Depends on the library but in short; yes. There are of course exceptions to this rule (for instance microsoft directx does not have this problem). Look through the documentation for the library and it will often tell you what versions it supports (and if your version is not supported it will, if open-source, often tell you how to compile the library aswell).
What do you mean "I wonder how the STL ever could get adapted by programmers under these preconditions."? STL is widely adopted by programmers but just like with any library, if you mix two versions; bad (and unforseen) things can (and probably eventually will) happend.
Sure, but in terms of STL I don't have any direct control about the library version I or other code I want to link uses.Originally Posted by Shakti
If I don't know with which compiler any module was built and I it also may be that the module utilizes the STL I basicly can't link against it.
Sure that problem exists with all libraries, but
a) most of the time they are linked dynamically so I just have the right verion to link against
and
b) they are not the so called _standard_ library of the programming system. Imo there shouln't be such pitfalls with it.
