Wrapping Qt container around standard container is quite a good idea to interact with other code. So Qt Container would be standard container + COW. One of the complains I hear very often is that Qt is an island and sadly in many cases I must agree. I think we should discuss the integration of the new library features too.
Cheers, Marco ________________________________ From: development-bounces+marco.bubke=theqtcompany....@qt-project.org <development-bounces+marco.bubke=theqtcompany....@qt-project.org> on behalf of Cristian Adam <cristian.a...@gmail.com> Sent: Thursday, June 25, 2015 1:18 PM To: Knoll Lars Cc: development@qt-project.org Subject: Re: [Development] Qt LTS & C++11 plans On Thu, Jun 25, 2015 at 1:04 PM, Knoll Lars <lars.kn...@theqtcompany.com<mailto:lars.kn...@theqtcompany.com>> wrote: Well, please tell me where this is such a big problem that we *have to have* VS2013 when it comes to our APIs. For our implementation inside Qt, we can work with slightly older compilers. It's not the end of the world and our users wouldn't even notice. Cheers, Lars There is always CopperSpice<http://www.copperspice.com/> the Qt fork which uses C++11. They've got rid of moc and plan to replace Qt containers with std ones. Afterwards maybe they will add support for namespaces to their peppermill source convertor utility. Cheers, Cristian.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
