On Mon, Jan 14, 2013 at 1:31 PM, Konstantin Tokarev <[email protected]>wrote:
> >> 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. > > > > But as John said a few mails ago, it seems the C is not enough to > implement all the required features. > > ICU provides C++ API but it does not use std::string. It operates on char > * or UnicodeString objects. > > std::string is just one case, the C++ API does allocate other objects and I'm sure that was what Yves (and me) wanted to highlight -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
