\r\n -confused [modified]
-
Hi! I can not figure this one out: I have two MFC-projects. One compiles in VS 2002 and one in VS 2005. At a certain point I have this line in both projects:
const TCHAR szHeaders[] = _T("Accept: text/*\r\nUser-Agent: XYZ\r\n");Now, in VS 2002 \r\n is intrepreted as a normal CRLF but not in VS 2005 it seems. (MS: "The _TCHAR data type is defined conditionally in Tchar.h. If the symbol _UNICODE is defined for your build, _TCHAR is defined as wchar_t; otherwise, for single-byte and MBCS builds, it is defined as char.") I have tried #undef _UNICODE without any luck! Debugger shows two squares: □□ like when !isascii() and does not break the line. Is it just the debugger or some conspericy going on here? -- modified at 7:35 Monday 5th February, 2007Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
-
Hi! I can not figure this one out: I have two MFC-projects. One compiles in VS 2002 and one in VS 2005. At a certain point I have this line in both projects:
const TCHAR szHeaders[] = _T("Accept: text/*\r\nUser-Agent: XYZ\r\n");Now, in VS 2002 \r\n is intrepreted as a normal CRLF but not in VS 2005 it seems. (MS: "The _TCHAR data type is defined conditionally in Tchar.h. If the symbol _UNICODE is defined for your build, _TCHAR is defined as wchar_t; otherwise, for single-byte and MBCS builds, it is defined as char.") I have tried #undef _UNICODE without any luck! Debugger shows two squares: □□ like when !isascii() and does not break the line. Is it just the debugger or some conspericy going on here? -- modified at 7:35 Monday 5th February, 2007Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
-
Hi! I can not figure this one out: I have two MFC-projects. One compiles in VS 2002 and one in VS 2005. At a certain point I have this line in both projects:
const TCHAR szHeaders[] = _T("Accept: text/*\r\nUser-Agent: XYZ\r\n");Now, in VS 2002 \r\n is intrepreted as a normal CRLF but not in VS 2005 it seems. (MS: "The _TCHAR data type is defined conditionally in Tchar.h. If the symbol _UNICODE is defined for your build, _TCHAR is defined as wchar_t; otherwise, for single-byte and MBCS builds, it is defined as char.") I have tried #undef _UNICODE without any luck! Debugger shows two squares: □□ like when !isascii() and does not break the line. Is it just the debugger or some conspericy going on here? -- modified at 7:35 Monday 5th February, 2007Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
*sniff* smells like something for the C++ forum...
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog
-
*sniff* smells like something for the C++ forum...
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog
-
*sniff* smells like something for the C++ forum...
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog
It's clearly just a rant. ;P
Gary Kirkham Forever Forgiven and Alive in the Spirit He is no fool who gives what he cannot keep to gain what he cannot lose. - Jim Elliot Me blog, You read
-
Could it be a mix up between the plain text return and the rich text return?
Brad Australian - Christian Graus on "Best books for VBscript" A big thick one, so you can whack yourself on the head with it.
Or some wierd compiler bug? - I mean since I have not added/removed any defines etc. Hmmmm...
Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
-
Hi! I can not figure this one out: I have two MFC-projects. One compiles in VS 2002 and one in VS 2005. At a certain point I have this line in both projects:
const TCHAR szHeaders[] = _T("Accept: text/*\r\nUser-Agent: XYZ\r\n");Now, in VS 2002 \r\n is intrepreted as a normal CRLF but not in VS 2005 it seems. (MS: "The _TCHAR data type is defined conditionally in Tchar.h. If the symbol _UNICODE is defined for your build, _TCHAR is defined as wchar_t; otherwise, for single-byte and MBCS builds, it is defined as char.") I have tried #undef _UNICODE without any luck! Debugger shows two squares: □□ like when !isascii() and does not break the line. Is it just the debugger or some conspericy going on here? -- modified at 7:35 Monday 5th February, 2007Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
Michael Mogensen wrote:
Now, in VS 2002 \r\n is intrepreted as a normal CRLF but not in VS 2005 it seems.
How are you verifying this?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
-
Could it be a mix up between the plain text return and the rich text return?
Brad Australian - Christian Graus on "Best books for VBscript" A big thick one, so you can whack yourself on the head with it.
-
Hi! I can not figure this one out: I have two MFC-projects. One compiles in VS 2002 and one in VS 2005. At a certain point I have this line in both projects:
const TCHAR szHeaders[] = _T("Accept: text/*\r\nUser-Agent: XYZ\r\n");Now, in VS 2002 \r\n is intrepreted as a normal CRLF but not in VS 2005 it seems. (MS: "The _TCHAR data type is defined conditionally in Tchar.h. If the symbol _UNICODE is defined for your build, _TCHAR is defined as wchar_t; otherwise, for single-byte and MBCS builds, it is defined as char.") I have tried #undef _UNICODE without any luck! Debugger shows two squares: □□ like when !isascii() and does not break the line. Is it just the debugger or some conspericy going on here? -- modified at 7:35 Monday 5th February, 2007Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
Maybe I missed it somewhere, but where are you using this char data? The interpretation of crlf and/or newlines varies by use.
-
Michael Mogensen wrote:
Now, in VS 2002 \r\n is intrepreted as a normal CRLF but not in VS 2005 it seems.
How are you verifying this?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
Just by looking into the buffer at a breakpoint after assignment/creation. It MUST be something I've missed but I just can't see it! I'll go into the hex tonight.
Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
-
Just by looking into the buffer at a breakpoint after assignment/creation. It MUST be something I've missed but I just can't see it! I'll go into the hex tonight.
Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
Michael Mogensen wrote:
Just by looking into the buffer at a breakpoint after assignment/creation.
Are you using var,s or var,su in the watch window?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
-
Michael Mogensen wrote:
Just by looking into the buffer at a breakpoint after assignment/creation.
Are you using var,s or var,su in the watch window?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
Is var,s and var,su some VS-setting or something? I don't know what I'm using... sorry... where do I check it?
Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
-
Is var,s and var,su some VS-setting or something? I don't know what I'm using... sorry... where do I check it?
Regards, Michael Mogensen, mm it-consult dk. ><((((º> ·.¸¸.· ><((((º> ·.¸¸.· ><((((º>
Michael Mogensen wrote:
Is var,s and var,su some VS-setting or something?
Yes, for the watch window.
Michael Mogensen wrote:
where do I check it?
See here.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb