--===============1661421167==
Content-Type: multipart/signed;
  boundary="nextPart2985865.qkV7ZXY8nO";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2985865.qkV7ZXY8nO
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 20 February 2007 00:46, Jon de Andr=E9s wrote:
> Hi!
> We can read in
> http://www.englishbreakfastnetwork.org/krazy/reports/bundled-apps/koffice=
/k
>ivio/index.html : "Adding single characters to a QString is faster if the
> characters are QChars and not QStrings. For example: QString path =3D old=
path
> + "/" + base is better written as QString path =3D oldpath + '/' + base" =
Is
> that correct?

Partly;

its better to use 'x' instead of "x" because 'x' maps to the native char=20
and "x" maps to a QString.
See the QString api docs for operator+=3D  there is a (char) version there.

Thanks for the patch :)
=2D-=20
Thomas Zander

--nextPart2985865.qkV7ZXY8nO
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQBF2svWCojCW6H2z/QRAhGWAKD4a8MLungxtW5kvF3bIB8c2eip/wCg0SmA
n1qjOudcaJsQb26x43c3w6s=
=Byx9
-----END PGP SIGNATURE-----

--nextPart2985865.qkV7ZXY8nO--

--===============1661421167==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1661421167==--