Thread: Memory reallocation

No, it's recv() Win32 API wont compile with std::string. Thanks though.
I hope it's good that way, I use memcpy() cause it's a binary string.

Code:

int main()
{
    char * Buf = new (nothrow)char[1024];
    if(Buf == 0) return 1;
    char Temp[1024];
    strcpy(Buf, "hello"); // just for the test
    memcpy(Temp, Buf, 6);

    delete[] Buf;
    Buf = new (nothrow)char[2048];
    if(Buf == 0) return 1;
    memcpy(Buf, Temp, 6);

    delete[] Buf;
    return 0;
}

Originally Posted by Ducky

No, it's recv() Win32 API wont compile with std::string.

That's rubbish. It will compile, otherwise your standard library or Windows API implementation is broken, or you are simply writing incorrect code.

That said, in the case of recv, it might be semantically better to use a std::vector<char> instead of a std::string since you're dealing with a buffer rather than a string.

Originally Posted by laserlight

That said, in the case of recv, it might be semantically better to use a std::vector<char> instead of a std::string since you're dealing with a buffer rather than a string.

And do not forget to resize (or create) your vector to be big enough to store the data you want to receive, and you actually put pointer to the first element and not the vector variable itself to your recv call as in laserlight's post #10

Originally Posted by phantomotap

O_o

In practice, few library implementations (I don't know of any; just hedging my bets.)

I prefer not to utilize the implementation defined behavior in my code as much as I can.

You were right Laserlight, recv() compiles with char vector.
Yahoo, no more messing around with pointers. ;-)