From kde-multimedia Fri Apr 12 10:41:23 2013 From: Harald Sitter Date: Fri, 12 Apr 2013 10:41:23 +0000 To: kde-multimedia Subject: Re: Review the patch Message-Id: X-MARC-Message: https://marc.info/?l=kde-multimedia&m=136576331508546 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============6668027985744538229==" --===============6668027985744538229== Content-Type: multipart/alternative; boundary=bcaec5215db58cd0df04da278c0e --bcaec5215db58cd0df04da278c0e Content-Type: text/plain; charset=UTF-8 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 --bcaec5215db58cd0df04da278c0e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, Apr 12, 2013 at 12:23 PM, Shubham Chaudhary <shubhamchaudhary92@gmail.com> wrote:
= I think QStrings are more efficient that normal strings.=C2=A0

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

HS=C2=A0
--bcaec5215db58cd0df04da278c0e-- --===============6668027985744538229== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-multimedia mailing list kde-multimedia@kde.org https://mail.kde.org/mailman/listinfo/kde-multimedia --===============6668027985744538229==--