get rid of extra copying (another one)

in the static toCFStringRef(const QString &string) method, the string's lifecycle
is unkown and thus, to ensure the data consistency, it copies the string's data
to the newly created CFStringRef object.

but operator CFStringRef() is an other case - here we know that the source string's
lifetime is limited by the same QCFString object as the resulting CFStringRef;
so, we could use the string's internal buffer as a CFStringRef's one w/o any
visible changes (well, except of some speed-up :) )

Merge-request: 2615
Reviewed-by: Denis Dzyubenko <denis.dzyubenko@nokia.com>

0 files changed, 0 insertions, 0 deletions