Printable View
Hi, I made a DLL to easily create windows and handle messages. I tried to use std::string for the class and title name, but it causes a crash on the client application. I changed the string type from std::string to char* and everything worked good.
Im confused here, what may be the problem?
Thank you
Don't forget to use the std::string member function c_str() when you are using it for something that requires a NULL terminated array of characters.
-Prelude
I do use c_str() of course. This problem exists *ONLY* in a DLL project. In a normal win32 app it works.. Other ideas?
Not a clue, perhaps the folks in the Windows forum could help you better.
-Prelude
k thanks.
im not sure how to fix it but its something about using the stl in a DLL, look on msdn for how to get around it.
I have noticed some issues when doing this myself. The best way to work around this problem is to either copy the string into a char array or to stick with char arrays and not use strings. The char array solution is best since if you absolutely need a string you can always make one using the char array.
c_str() gives me invalid data sometimes, any idea on that too?
I mean I convert a String to a Char using the c_str() function and it would give me something like "[][]|||^*" back, unless there is better ways off converting a String to a char* ?
I've has similar problems with the vector template class.
best bet is don't use stl objects across DLL's. Really you ought to make your DLL interfaces flexible enough to use in other languages so STL objects as parameters are obviously out.
It's due to static members in the Dinkumware STL classes.
http://support.microsoft.com/default...EN-US;Q172396&
It might be fixed in VC.NET (I haven't tried), or you could use an alternative STL implementation.
I see! I could use const char and char, but I am not thinking of only string. I need to use the vector template later too. What do you mean by other stl implementations?
JoeSixpack: Thanks for the info!! :D
> best bet is don't use stl objects across DLL's.
FillYourBrain is right. It is a very precarious to pass objects between a DLL & client application. This is because both object internals must match on a byte per byte basis between client & DLL, otherwise disasterous things happen. This is especially true if the DLL was written with one compiler & the client with another. But you will no doubt run into problems in anycase even if using the same compiler.
Unless you want to get into pure virtual class interfaces and/or COM, I suggest you don't pass object between your client & DLL.