There are two reasons that urged me to create one more string class, in spite of the fact that so many of them already exist. Let s consider the following scenarios:



TCHAR-based application extensively using COM, the functions/interface methods of which are WCHAR-based.

TCHAR-based application working with network protocols, which normally make use of ASCII.

Passing strings across module borders (between an executable and a DLL or between DLLs). In this situation, strings are required to use some global memory allocator (such as GlobalAlloc, CoTaskMemAlloc, or VirtualAlloc).

Necessity to have strings that are compared case-insensitively by default. Sometimes, it is desirable as well to compare case-sensitive strings in a case-insensitive manner and vice versa.

Any combination of the previous scenarios or any situation when different kinds of strings must be used jointly.

-There are two reasons that urged me to create one more string class, in spite of the fact that so many of them already exist. Let s consider the following scenarios: TCHAR-based application extensively using COM, the functions/interface methods of which are WCHAR-based. TCHAR-based application working with network protocols, which normally make use of ASCII. Passing strings across module borders (between an executable and a DLL or between DLLs). In this situation, strings are required to use some global memory allocator (such as GlobalAlloc, CoTaskMemAlloc, or VirtualAlloc). Necessity to have strings that are compared case-insensitively by default. Sometimes, it is desirable as well to compare case-sensitive strings in a case-insensitive manner and vice versa. Any combination of the previous scenarios or any situation when different kinds of strings must be used jointly.