This EE article provides examples of conversion techniques for various types of string variables: classic C-style strings, MFC/ATL CStrings, and STL's std::string data type.
Convert Integer to String
int to C-style (NULL-terminated char) string
int to ATL/MFC CString
sprintf( szResult, "%d", n ); // use "%u" for unsigned int
sprintf_s( szResult, sizeof(szResult), "%d", n ); // "safe" version
//------------------------------------- alternative: itoa
_itoa( n, szResult, 10 );
_itoa_s( n, szResult, sizeof(szResult), 10); // "safe" version
int to STL std::string
sResult.Format( "%d", n ); // use "%u" for unsigned int
ostr << n;
Convert String to Integer
C-style (NULL-terminated char) string to int
ATL/MFC CString to int
char szNumber= "1234567890";
nResult= atoi( szNumber );
STL std::string to int
CString sNumber= "1234567890";
nResult= atoi( sNumber ); // automatically does LPCSTR(sNumber)
std::string sNumber= "1234567890";
nResult= atoi( sNumber.c_str() );
If you are using the UNICODE character set and supplying an output buffer (as with sprintf and itoa) you'll need to keep in mind that characters are two bytes long. The normal procedure is to declare character buffers as the TCHAR data type, which will take into consideration the data element size.
Output buffer length.
C++ integers are typically 32-bits, with values as high as billions; the range is: 0 to 4,294,967,295 (unsigned)
-2,147,483,648 to 2,147,483,647 (signed)Thus, the maximum length of the resulting string is 12 characters (including NULL terminator and not including commas or other formatting).
If you are working with 64-bit integers (called __int64 or long long), the values are as high as quintillions; the range is: 0 to 18,446,744,073,709,551,615 (unsigned)
-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 (signed)Thus, the maximum length of the resulting string is 21 characters (including NULL terminator and not including commas or other formatting).
Both sprintf and itoa have been termed unsafe (some would say they've been deprecated, others would not use that term) because of the chance that a sloppy programmer might not provide a large enough output buffer.
The examples show how to use the safer xxx_s variations of these functions as an alternative. The older functions might write beyond the end of the buffer and stomp on other variables or blow the stack frame -- and cause endless debugging headaches. Of course, if you are determined to give yourself grief, you can still blow up the "safe" version by passing in the wrong length value...
The CString::Format function allocates the buffer for you and takes care to avoid the buffer overrun problem. The std::ostringstream << (insertion operator) also takes care of the buffer allocation for you.
The examples above compile and work under Microsoft VS2008. Some Microsoft-specific functionality is implied (refer to the references, below, if you worry about these things). However, there is an excellent chance that at least one of the variations will work for you in your development system, whatever it is.
atoi, _atoi_l, _wtoi, _wtoi_l
sprintf, _sprintf_l, swprintf, _swprintf_l, __swprintf_l
_itoa, _i64toa, _ui64toa, _itow, _i64tow, _ui64tow
String to Numeric Value Functions
If you liked this article
and want to see more from this author,
please click the Yes
button near the:
Was this article helpful?
label that is just below and to the right of this text. Thanks!