I get the impression STLport has substantial potential performance gains over Dinkumware's STL - so I'm considering porting a large MSVC solution to STLport to try it out. The solution has several external dependencies, some of them 3rd party. I see vague mentions of linkage/runtime issues to be expected - must indeed such a migration be done in a single stroke, on all dependencies? Isn't there a way to partially port the solution? Would I be losing the performance gains if I do?
The solution is an MFC app, ~80 projects, currently compiled on VS2005 but soon to be ported to VS2010.