[Development] Dropping QT_NO_STL (was: The future of QtAlgorithms)
thiago.macieira at intel.com
Mon Jan 30 23:03:22 CET 2012
On Monday, 30 de January de 2012 18.38.56, João Abecasis wrote:
> On 30. jan. 2012, at 17.25, ext Thiago Macieira wrote:
> > My point here and below with "the containers themselves" is that we don't
> > want to use those containers in our code nor in our API.
> What's wrong with using them in our code, as long as they stay out of the
> std::vector is perfectly fine for a non-shared dynamically allocated array.
I'd like our containers to be good enough for that, to be honest. And avoid
subtle mistakes if the behaviour differs.
But where it makes sense, sure. Roberto used STL in the his C++ parser.
Just avoid "template bloat": out-of-line copies of identical code because the
compiler can't figure out two functions do the same. It's hard to measure.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/development/attachments/20120130/4b1fb189/attachment-0001.bin
More information about the Development