Click here to Skip to main content
15,499,571 members
Articles / Programming Languages / C++
Posted 28 May 2001

Tagged as


227 bookmarked

CString-clone Using Standard C++

Rate me:
Please Sign up or sign in to vote.
4.93/5 (128 votes)
7 Dec 2011CPOL4 min read
A Drop-In replacement for CString that builds on the Standard C++ Library's basic_string template


As much as I use and appreciate the Standard C++ Library, I've never liked its string template - basic_string<>. At times, it seems the designers went out of their way to make it difficult to use.

On the other hand, I've always loved the ease of use of MFC's CString class. It checks for NULL pointers, implicitly converts to const TCHAR*, and has some very handy member functions (Format, Load, etc.) that make string programming a breeze. But of course, I don't want to use MFC anymore. In fact, I don't want to rely on any proprietary library because I want portability.

Therefore I decided to combine the best of both worlds and create:


This is a class (a template instantiation actually) that derives from from basic_string<TCHAR>. To the basic_string it adds the entire CString API. You get CString ease of use with 100% basic_string compatibility. In short, a CStdString object is a basic_string that (with very few exceptions (noted below) it is also a drop-in replacement for CString. The best part of this is that both APIs (basic_string and CString) are well known and well documented.

I originally submitted this article to another code site (which shall remain nameless :)) a few years ago. I like CodeProject so much I thought I'd submit it here too. I have used this class in almost every professional project I've done over the past 4 years. It has proven to be the single most useful piece of code I've ever written. It is also extensively debugged. I hope you like it. If you ever have any problems with it, please e-mail me. I'm happy to help.

I provided a simple source application here to prove some of the CString functions work but it's really just a token. The list of sample projects out there that use CString and/or basic_string is massive.


  • Drop in Replacement for CString (see below for exceptions)
  • Two instantiations available at all times -- wchar_t-based version CStdStringW and char-based version CStdStringA. The name CStdString is just a typedef of one of these two.
  • Safely checks for NULL string pointer inputs (like CString) in all functions
  • Extra constructors and assignment operators to automatically convert between wide (wchar_t-based) and thin (char-based) strings for you.
  • Implicit conversion to c_str(). The C++ committee doesn't like this but I sure do.
  • Builds on several platforms, including Windows, Unix and Linux. Works with several implementations of the Standard C++ Library, including Dinkumware, GNU, CodeWarrior, and STLPort.
  • Win32 builds give you some extra goodies like UNICODE/MBCS conversion macros (just like MFCs) as well as member functions for persisting CStdString objects to and from DCOM IStreams.
  • Makes no use of any implementation details of the base class template (basic_string)
  • The derived template adds no member data to basic_string and adds no virtual functions

There are a couple of issues about this code of that I should point out.

CString Compatibility

I was unable to exactly reproduce the CString API. There are a two functions that both CString and basic_string; share, but implement differently. In these cases, I felt it best to make CStdString behave like basic_string (the base class) rather than CString. To be specific.

  • CStdString::operator[] returns characters by value (unlike CString which returns them by reference)
  • The constructor that takes a character and a count takes them in the order (count, value) which is the opposite of the order CString declares them. That's the order that basic_string<>; needs and it was impossible to implement both versions.

There were also two CString functions I could not implement at all -- LockBuffer and UnlockBuffer.

Deriving From basic_string<>

The template I wrote derives from basic_string, a class template without a virtual destructor. Any introductory text to C++ will tell you that it is dangerous to derive from a class without a virtual destructor. It can lead to behavior that is undefined. So if you were to code the following (deleting a CStdStringA through a pointer to the base class), you would technically get undefined behavior:

// assign DERIVED object to  BASE pointer
std::string* pstr = new CStdStringA("Hi"); 

// delete  DERIVED through BASE class pointer -- UNDEFINED
delete pstr;   

Personally, I don't think this is much of an issue. I mean really how often do you actually do this with string objects? I have rarely (if ever) needed to dynamically allocate a string object on the heap. And if I ever do, I won't using a base-class pointer. So if you don't do this, you'll never have to worry. In fact, even if you do code this way, I doubt you'll have any problems with CStdString. I can tell you that at least with Microsoft Visual C++, even the above code runs just fine with no errors or memory leaks. I doubt many other compilers would give you problems either. However my doubt does not impose reality on the C++ world. Caveat Emptor.


  • 7 Dec 2011: Updated source code.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By
Web Developer
United States United States
I've been a software developer since 1990.

While my main page is out of date (and I have therefore blanked it), you can read about the CStdString pages here

Comments and Discussions

GeneralGreat Code Pin
JeffBilkey14-Dec-11 15:41
MemberJeffBilkey14-Dec-11 15:41 
GeneralRe: Great Code Pin
Joe O'Leary28-Dec-11 9:02
MemberJoe O'Leary28-Dec-11 9:02 
QuestionRe: Great Code Pin
User 340137514-May-12 8:40
MemberUser 340137514-May-12 8:40 
GeneralMy vote of 5 Pin
Terry Wells12-Dec-11 9:52
MemberTerry Wells12-Dec-11 9:52 
QuestionVS2010 unresolved symbols Pin
sisira10-Dec-11 21:05
Membersisira10-Dec-11 21:05 
AnswerRe: VS2010 unresolved symbols Pin
Joe O'Leary11-Dec-11 3:52
MemberJoe O'Leary11-Dec-11 3:52 
QuestionWhere is the latest code? Pin
sisira10-Dec-11 19:47
Membersisira10-Dec-11 19:47 
AnswerRe: Where is the latest code? Pin
Joe O'Leary10-Dec-11 20:54
MemberJoe O'Leary10-Dec-11 20:54 
No the date of the latest code is just a couple of days ago

GeneralRe: Where is the latest code? Pin
sisira10-Dec-11 21:01
Membersisira10-Dec-11 21:01 
Questiongcc compilation errors Pin
mirko busto9-Dec-11 1:33
Membermirko busto9-Dec-11 1:33 
AnswerRe: gcc compilation errors Pin
Joe O'Leary9-Dec-11 4:59
MemberJoe O'Leary9-Dec-11 4:59 
Questionfind two a small bug~ Pin
dnybz9-Dec-11 1:17
Memberdnybz9-Dec-11 1:17 
AnswerRe: find two a small bug~ Pin
Joe O'Leary9-Dec-11 4:56
MemberJoe O'Leary9-Dec-11 4:56 
GeneralRe: find two a small bug~ Pin
dnybz9-Dec-11 5:08
Memberdnybz9-Dec-11 5:08 
GeneralRe: find two a small bug~ Pin
Joe O'Leary9-Dec-11 5:37
MemberJoe O'Leary9-Dec-11 5:37 
GeneralRe: find two a small bug~ Pin
dnybz9-Dec-11 6:05
Memberdnybz9-Dec-11 6:05 
GeneralRe: find two a small bug~ Pin
Joe O'Leary9-Dec-11 6:16
MemberJoe O'Leary9-Dec-11 6:16 
GeneralRe: find two a small bug~ Pin
dnybz9-Dec-11 6:21
Memberdnybz9-Dec-11 6:21 
GeneralRe: find two a small bug~ Pin
Joe O'Leary9-Dec-11 7:18
MemberJoe O'Leary9-Dec-11 7:18 
GeneralMy vote of 5 Pin
Albert Holguin7-Dec-11 6:07
professionalAlbert Holguin7-Dec-11 6:07 
GeneralRecommended Pin
Petr Prazak7-Dec-11 1:02
MemberPetr Prazak7-Dec-11 1:02 
GeneralRe: Recommended Pin
Joe O'Leary9-Dec-11 5:00
MemberJoe O'Leary9-Dec-11 5:00 
QuestionGreat, but... Pin
qiuqianren6-Dec-11 22:26
Memberqiuqianren6-Dec-11 22:26 
AnswerRe: Great, but... Pin
Joe O'Leary7-Dec-11 4:10
MemberJoe O'Leary7-Dec-11 4:10 
GeneralMy vote of 5 Pin
roman3136-Dec-11 21:03
Memberroman3136-Dec-11 21:03 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.