Search:

Here's the way I look at it. When I program for Windows, I wrap any string or char literals in _T() and I never have to worry about it.

It depends how temp is defined. If defined as char[], then you won't get errors. If defined as wchar_t[], then you should. I find developers have the least amount of trouble when coding in windows...

Yes.



if( temp[pos] == _T('p') || temp[pos] == _T('P') )
{

}

While you *can* have both ANSI and UNICODE in a single program, I'd recommened that you compile your program for all UNICODE. If you have data coming in (or going out) that's then convert the data...

This really is more of the VC and windows environment than MFC. The bottom line is that if you use _T("") around string literals, it will work for both. If you use "" or L"", you could run into...

You can also use the conversion macros.




USES_CONVERSION;

std::wstring val
CString src