Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I keep reading that if the DLL is linked against another version of the runtime that doesn’t match the other modules using it and it returns a std:: object or one of its classes has std:: arguments, it will cause the program to crash. How does SFML do it then? I do not see any warnings about this anywhere and they heavily use std:: ..
Thanks
In theory, there are no guarantees of interoperability between different C++ runtimes, not even between different releases of the same compiler. And it seems that SFML releases
separate Windows library downloads for VC++ 2005, VC++ 2008, and MinGW.
But to say that mixing different runtimes will cause a crash is an exaggeration. If compiler vendors didn’t maintain some reasonable level of interoperability (for example, between minor patches to major compiler releases), their customers would run for the hills, or at least they would if they had a lick of sense!