--===============1275833961==
Content-Type: multipart/signed;
  boundary="nextPart1995462.PfvimygHCm";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1995462.PfvimygHCm
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

is there a reason why Value does not use the implicitly sharing offered by =
Qt?=20
I remember one bug (zeros all over), that was caused by a missing detaching=
=20
of the data. I'd prefer Qt's built-in way, as it pulls the whole logic behi=
nd=20
the scenes and opens the door for multi-threading.

Should it be converted or should it stay as is until multi-threading takes=
=20
place? Or is there any other good reason for the one or the other?

Regards,
Stefan

--nextPart1995462.PfvimygHCm
Content-Type: application/pgp-signature

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

iD8DBQBFp75ApfDn2DABIpcRAqSqAJwI2JOK6RDbrczf7CTbX1UUcOebLwCgrUHi
LhazFu6wWsnwKH6it0h7oTg=
=03dE
-----END PGP SIGNATURE-----

--nextPart1995462.PfvimygHCm--

--===============1275833961==
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

--===============1275833961==--