With the current standard (the upcomming standard differs here) there is no guarantee that the internal memory buffer managed by the std::string
will be contiguous, or that the .c_str()
method returns a pointer to the internal data representation (the implementation is allowed to generate a contiguous read-only block for that operation and return a pointer into it. A pointer to the actual internal data can be retrieved with the .data()
member method, but note that it also returns a constant pointer: i.e. it is not intended for you to modify the contents. The buffer return by .data()
it is not necessarily null terminated, the implementation only needs to guarantee the null termination when c_str()
is called, so even in implementations where .data()
and .c_str()
are called, the implementation can add the
to the end of the buffer when the latter is called.
The standard intended to allow rope implementations, so in principle it is unsafe to do what you are trying, and from the point of view of the standard you should use an intermediate std::vector
(guaranteed contiguity, and there is a guarantee that &myvector[0]
is a pointer to the first allocated block of the real buffer).
In all implementations I know of, the internal memory handled by std::string
is actually a contiguous buffer and using .data()
is undefined behavior (writting to a constant variable) but even if incorrect it might work (I would avoid it). You should use other libraries that are designed for this purpose, like boost::format
.
About the null termination. If you finally decide to follow the path of the undefined... you would need to allocate extra space for the null terminator, since the library will write it into the buffer. Now, the problem is that unlike C-style strings, std::string
s can hold null pointers internally, so you will have to resize the string down to fit the largest contiguous block of memory from the beginning that contains no
. That is probably the issue you are finding with spurious null characters. This means that the bad approach of using vsnprintf
(or the family) has to be followed by str.resize( strlen( str.c_str() ) )
to discard all contents of the string after the first
.
Overall, I would advice against this approach, and insist in either getting used to the C++ way of formatting, using third party libraries (boost is third party, but it is also the most standard non-standard library), using vectors or managing memory like in C... but that last option should be avoided like the plague.
// A safe way in C++ of using vsnprintf:
std::vector<char> tmp( 1000 ); // expected maximum size
vsnprintf( &tmp[0], tmp.size(), "Hi %s", name.c_str() ); // assuming name to be a string
std::string salute( &tmp[0] );
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…