operator overloading

[NMTop40]

What is operator+ supposed to do? Why work with a temporary char* when you can work with a temporary FunnyString that is returned? Have you considered implementing operator+=, then possibly implementing operator+ by using operator+=?

EDIT:

Sounds possible, but I cannot find where dakotabk made the mistake of setting the data member variable to anything other than the result of new[] or a null pointer constant.

He was going to change it to point to an empty string.

As for operator+, it is to allow efficient implementation of this that the standard does not require that it internally holds a contiguous buffer. Effectively you can have a variation of a string that has two or more pointers concatenated together (A rope, I think they call it).

It is relatively easy to implement a string that works. It is extremely difficult to implement one that works well in all (or at least the most common) situations.

[Lindley]

The problem is, when an object contains pointer and destructor also ( destruct this pointer ), you can not return this object , don't you?

That's what the copy constructor is for. In this code:

MyClass dosomething(const MyClass &mc1, const MyClass &mc2)
{
    MyClass result;
    // stuff
    return result;
}

Then indeed, result's destructor will be called at some point; but only *after* the copy constructor is used to take its relevant values to whatever is waiting outside the function to receive them.