[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-multimedia
Subject:    Re: Review the patch
From:       Harald Sitter <sitter.harald () gmail ! com>
Date:       2013-04-12 10:41:23
Message-ID: CAEc+18E3dqSTSPnXzzQ-4k7Ww9MdvLTzo02LNQ06FGeYGgoAVQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, Apr 12, 2013 at 12:23 PM, Shubham Chaudhary <
shubhamchaudhary92@gmail.com> wrote:

> I think QStrings are more efficient that normal strings.
>

That is not true by the way. QStrings are larger than char* (as they
support unicode etc.etc.). Also constructing a QString is more expensive as
they need to convert whatever you enter into UTF-16. So when a string can
only contain ASCII characters it is usually advisable to use a char*.

HS

[Attachment #5 (text/html)]

<div dir="ltr">On Fri, Apr 12, 2013 at 12:23 PM, Shubham Chaudhary <span \
dir="ltr">&lt;<a href="mailto:shubhamchaudhary92@gmail.com" \
target="_blank">shubhamchaudhary92@gmail.com</a>&gt;</span> wrote:<br><div \
class="gmail_extra">

<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I think QStrings are \
more efficient that normal strings.  </div></blockquote><div>

<br></div><div style>That is not true by the way. QStrings are larger than char* (as \
they support unicode etc.etc.). Also constructing a QString is more expensive as they \
need to convert whatever you enter into UTF-16. So when a string can only contain \
ASCII characters it is usually advisable to use a char*.</div>

<div style><br></div><div style>HS  </div></div></div></div>



_______________________________________________
kde-multimedia mailing list
kde-multimedia@kde.org
https://mail.kde.org/mailman/listinfo/kde-multimedia


[prev in list] [next in list] [prev in thread] [next in thread]