std::string problem.

Edit: Let me rephrase that. There is no special way to convert a char-pointer string to a std::string. Your assignment operation (std::string strNodeName = szNodeName; ) is perfectly fine.

Some more info might be helpful. For example, are you using a certain library for loading the XML file? If so, does it require you to release it/clean up somehow?

I'm using tinyXml.
Actually this errors happens not only in xml parser. DevPartner always shows this error when i'm trying to convert char * to std::string by =.

I've got that warning as well. It seems alright to me, although i don't like having warnings around.

std::string seems to check, if the passed pointer is maybe inside its own buffer. This triggers the warning that two unrelated pointers are being compared (well they are). This might be a problem in other cases but in this case it's only a sanity check.

Quote:

Original post by Programmer16 Edit: Let me rephrase that. There is no special way to convert a char-pointer string to a std::string. Your assignment operation (std::string strNodeName = szNodeName; ) is perfectly fine. Some more info might be helpful. For example, are you using a certain library for loading the XML file? If so, does it require you to release it/clean up somehow?

First I apologise cause at work we mainly do C although I am currently pushing development to C++. Therefore I hardly have any experience with std::string

But at home I am writing some stuff for myself and to use a string from char_t (I need it so I can convert a wxString to string) I tend to do:

std::string newstring(char_pointer);

this seems to work fine and running in debug is not showing up any mem leaks when I close the application. Maybe thats the problem? I never tried simply assigning it straight away.

By the way, limpacp, you say you have mem leaks... that szNodeName refers to a char[] right? not a pointer that was allocated somewhere and never freed?


Hope it helps.

std::string newstring(char_ptr);

is equivalent to

std::string newstring=char_ptr;

since the second one just translates to a call to the constructor

string::string(const char *s);

I imagine that your problem either lies elsewhere or that the consequences of this one go deep. Protected mode apps have no direct way of interfering with one another. Unless you are leaking your system out of pageable memory or are using a common interface that has its own system-wide resource management, there should be no way (outside of the absurd, such as WriteProcessMemory()) that your app can cause Photoshop to fail.

Also, I think DevPartner is perhaps just being a little too thorough. That pointer comparison looks valid to me. Granted, the sources are nowhere near each other, but 0x0012FAA4 is bang in the middle of your stack and 0x02402F48 looks like it's way up in himem, probably part of the global heap (or possibly in a DLL .xdata section). This suggests to me that the STL is simply performing a sanity check, to prevent unnecessary string copies, or perhaps a bounds check. I couldn't say for sure without seeing the STL code responsible, but I think you should look elsewhere for the source of your memory leaks.

Regards
Admiral