C / C++ / MFC

elelont2 wrote:

I am reading the following code example returning char* from function:

http://www.java2s.com/Tutorial/Cpp/0140__Function/Returnapointerfromafunction.htm

elelont2 wrote:

So it is not even safe to return ss.str() since stringstream goes out of scope?

string Convert(int val)
{
//...
}

CPallini wrote:

since the return value would be a copy of the string object.

Erudite_Eric wrote:

Ever wondered why C++ can be so heavy on the stack?

Erudite_Eric wrote:

What he can do of course is pass a SS as a pinter to the func, which allocates enough storage, does its thing, and returns success or fail. Then the caller can free the storage when it has to.

<pre lang="c++">
func()
{
const char* test = "hello";

MyClass* my = new MyClass(test); //does test variable go out of scope here? 

//test variable exists here
return my; //now test variable goes out of scope
}

<pre lang="c++">
func()
{
const char* test = GetString().c_str();
std::cout << test << std::endl; //Here test prints correct value

MyClass* my = new MyClass(test); //does test variable go out of scope here? 

//test variable exists here
return my; //now test variable goes out of scope
}

CPallini wrote:

Passing a reference it is usually better.

Erudite_Eric wrote:

Ever seen C++ code disassembled?