C / C++ / MFC

char *str = new char [10];
strcpy(str,"hello\r\n");
int x = strlen(str);
str[x-2] = '\0';
x = strlen(str);
delete[] str;

samkook wrote:

It won't work, because i can have up to 3 /r/n in the string.

samkook wrote:

Also do you know if CFile.write will write the null to the file? I was wondering if it could be the reason why I can't add a null to a string.

samkook wrote:

strInfo->Replace("\r\n","\0");

<br />
		char str[20]; // or char *str = new char [20];<br />
		int index;<br />
<br />
		strcpy(str, "hello\r\n");<br />
		index = strlen(str);<br />
<br />
		if(index) {<br />
			index--;<br />
			for(; index >= 0; index--) {<br />
				if(str[index] == '\r' || str[index] == '\n') str[index] = '\0';<br />
				else break;<br />
			}<br />
		}<br />
<br />
		// str is now stripped from trailing CR LF combinations and NULL terminated<br />
<br />
		// If alloced with new<br />
		// delete[] str;<br />

waldermort wrote:

I've heard of differences between debug and release builds, but never of with the bugger or without. I have a very simple console app printing the length of unicode strings to the screen. With a debug version, one of the values is being displayed wrong (should be 4 but shows 10). If I step through the code, it's correct, it display the correct value to the screen. If I hit the run button, the value is wrong. Any idea what could be causing this? Does the debugger make any changes to the code or any changes to the memory managment?