Im afraid the junk string is passed to the funtion that requires it.
I'm using VC7.0 so I would assume that the <string> implementation cannot be "that" buggy. Can it?
In which case, would you expect
cs1 = m_sRootURL.Left(10);
s1 = (LPCTSTR)cs1;
cs1 = m_sRootURL.Mid(10,10);
s1 += (LPCTSTR)cs1;
to work?
The first call is fine, the second junks the <string>.
If the <string> is initailzed correcly {as in string("")}. the junking takes the form of...
chipper, no its not.
This was(is) test code to see what was happening in the app whilst debugging. Is more than 20 chars (typical ftp URL).
The idea of the code above was to see how many chars i could transfer (as I have other vars that were transfering with no problems at all)...
Hi all
Imconfused by a daft problem..
Our apps are written using MFC (CStrings etc) but we are using a library which uses ATL (strings). I understand tstring is a basic string but cant get my head around this simple problem...
I cannot assign a tstring longer than 15 chars...
To show an...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.