>>60
Is everything in the STL usually mucked up across implementations, or only the really hairy containers like hashtables and treemaps and such? I've only used vectors so far in my game, but if worse comes to worst when I finish it and have troubles porting it, it shouldn't be hard to write my own resizeable array container.
I know for a fact John Carmack re-invents the wheel always specifically to make porting a cinch rather than a chore... sure, it adds a whole year of development time to a game when he COULD use the standard routines of C and C++, but it also makes *maintenance* easy -- when there's a bug in an id game, you immediately know, somewhere, it's id-caused, NOT caused by some third-party library or standard library routine has an unknown bug in it.