sf::String and std::string::c_str in SFML2

[Groogy]

Just wondering, is this intended behavior? I had this code:

Code: [Select]

const char * cString = string.ToAnsiString().c_str();
FILE * file = fopen(cString, "rb");

Opening the file would fail and when I debugged and looked at cString it would contain junk data. But if I skip the middle hand cString pointer and only write:

Code: [Select]


FILE * file = fopen(string.ToAnsiString().c_str(), "rb");

the file is actually opened and apparently it contains the proper characters.

Is this how it is intended to be designed or is std::string messing with me?

[Silvah]

It is how the language works. The temporary std::string created by a call to the ToAnsiString method lasts "to the semicolon", that is, it is destroyed at the end of the statement that created it.

[Laurent]

You must store the returned std::string, not a pointer to its content. Otherwise, like Silvah explaines, the std::string is destroyed and the pointer points to invalid data.

Code: [Select]

std::string cString = string.ToAnsiString();
FILE * file = fopen(cString.c_str(), "rb");

[Groogy]

Aight then it's intended behavior

Anyway I was just checking in so it wasn't a unkown bug.