«

ostrstream m_msgStream;
m_msgStream.seekp(0);
m_msgStream << "Hello";
m_msgStream << ends;
char *str = m_msgStream .str();

We are getting str NULL. If we remove the skeep line then it working
fine. Even the same code is working fine with VS 6. Anyidea how to use
seekp in VS 2008?

On 02/15/2011 11:44 AM, Saurabh Gupta wrote:
> ostrstream m_msgStream;
> m_msgStream.seekp(0);
> m_msgStream<< "Hello";
> m_msgStream<< ends;
> char *str = m_msgStream .str();
>
> We are getting str NULL. If we remove the skeep line then it working
> fine. Even the same code is working fine with VS 6. Anyidea how to use
> seekp in VS 2008?

Why use it at all? At least it is entirely superfluous in the example
code you posted.

Aside from that, you should realize that std::stringstream::str()
returns std::string, not char*. You should be using:

const char *str = m_msgStream.str().c_str();

Please note that modifying the contents of the return value of
std::string::c_str(), as might happen after the above assignment to
non-const char* (which is allowed for legacy reasons on many compilers),
will result in undefined behavior (c_str() returns const char*).

On 02/15/2011 07:13 PM, Paavo Helde wrote:
> Robert Hairgrove<> wrote in news:14522$4d5ab628
> $d9a2e747$:
>
>> On 02/15/2011 11:44 AM, Saurabh Gupta wrote:
>>> ostrstream m_msgStream;
>
> ostrstream has been deprecated for a long time already, I would suggest
> to switch over to ostringstream.
>

Oops ... overlooked that one!

>> Aside from that, you should realize that std::stringstream::str()
>> returns std::string, not char*. You should be using:
>
> He is using ostrstream, where indeed str() returns char*.

Oops again.

>> const char *str = m_msgStream.str().c_str();
>
> With ostringstream this would create a dangling pointer into a destroyed
> temporary std::string object!

And yet another oops!