Em Monday, 27 de June de 2011, às 10:52:55, André Pönitz escreveu: > > Any thoughts? > > I think it boils down to the question > > Does Qt 5 have to support compilers that don't "do" C++0x ? > > If yes, then we are basically back to the VC6 times when the interface was > sprinkled with #ifdef's due to the missing member template support there.
I think the answer is very clear for the next two or three years:
Qt must compile in either way and must provide THE SAME ABI. That is, if you
enable C++0x, it should not create any extra symbols. And if you don't compile
that, then you can still use C++0x features in your code, along with Qt.
We've so far been able to do that. The only thing I have tried so far and
haven't been able to keep completely inline is move constructors for classes
with non-inline Privates. I also expect that we'll be unable to use rvalue-
this for non-inline classes.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
