C / C++ / MFC

case WM_FILE_DOWNLOAD_PROGRESS_AVAILABLE:
    progHdr = (downloadHeader_t*)lParam;

    if (progHdr->bComplete)
        sprintf(buffer, "Complete");
    else
    {
        if (progHdr->contentLen > 1024*1024)
            sprintf(buffer, "%.2f MB", (float)progHdr->contentLen / (1024*1024) );
        else if (progHdr->contentLen > 1024)
            sprintf(buffer, "%.1f KB", (float)progHdr->contentLen / (1024) );
        else
            sprintf(buffer, "%d B", progHdr->contentLen);
    }

    setListViewItemDownloaded(listWnd, (int)progHdr->lParam, buffer);

    return true;

Codling2020 wrote:

reading material that might be useful

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
}