Re: QCString construction

On Sunday 11 February 2007 00:11, David Faure wrote:
> On Saturday 10 February 2007, Roger Larsson wrote:
> > Have you benchmarked that your Qt patch really is faster?
>
- - -
> Results:
> Initial operator+ took 956 milliseconds
> My operator+ took 731 milliseconds
>   (... still slow because QCString::operator+=( const char *str ) is
> called, which calls qstrlen(str), but I can't avoid that one; stupid
> qcstring doesn't store its own length.)
> Yet, it is a 23% speed improvement already.

Ouch!

/RogerL