stdext::hash_map vc8
Author
http://msdn2.microsoft.com/en-US/library/ek139e86(VS.80).aspx
since when did they start to care :)
since when did they start to care :)
Yeah, that confused the hell out of me when all my code broke converting from VS7 to 8. Makes sense though.
Quote:Original post by python_regious
Yeah, that confused the hell out of me when all my code broke converting from VS7 to 8. Makes sense though.
Sadly, it always makes sense when it becomes a big problem for everyone else.
Didn't anybody at Microsoft know that it wasn't part of the standard in the first place?
Quote:Original post by owlQuote:Original post by python_regious
Yeah, that confused the hell out of me when all my code broke converting from VS7 to 8. Makes sense though.
Sadly, it always makes sense when it becomes a big problem for everyone else.
Didn't anybody at Microsoft know that it wasn't part of the standard in the first place?
Microsoft knew a lot of things weren't part of the standard in the first place, and did them anyhow. At some point, you have to admit that you fucked up in the past and do the right thing from there on. In this case, moving those non-standard structures into non-standard namespaces is the right thing to do.
That said, MS provides a flag to move them back into std::. So if your code breaks and you don't want to fix it, just enable MS extensions and disable the resulting warning. Problem solved.
CM
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
