[Development] ICU and Windows

Thiago Macieira thiago.macieira at intel.com
Mon Jan 14 09:35:35 CET 2013


On segunda-feira, 14 de janeiro de 2013 08.31.19, Yves Bailly wrote:
> Which is not always that easy... if a library function returns, say, an
> simple std::string *by value*, then who will destroy the allocated memory?
> It's really too easy to break something, somwhere, causing a random crash
> almost impossible to reproduce reliably.

The ICU C API does not use std::string: it was meant to be used from C code. 
It's quite easy to avoid std::string in that case.

> The nice thing with Qt is that everything really needed was provided with Qt
> itself in its 3rdparties: libjpeg, libpng, sqlite... If ICU is a "hard"
> need, then IMHO it's a good candidate to be provided alongside the other
> 3rdparties.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130114/5c1bb24f/attachment.sig>


More information about the Development mailing list