3 ms·
QT's move to modern C++ standards gives the "which cross-platform C++ framework should I use to create my app" another data point. Want to use the latest C++ f
by rpwilcox 14y ago
QT's move to modern C++ standards gives the "which cross-platform C++ framework should I use to create my app" another data point.
Want to use the latest C++ features? QT has your back. Not a fan of modern C++? wxWidgets has your back.
- icefox 14y agoSounds like you didn't read the article. For example rather than using 'override' if you use the Q_DECL_OVERRIDE macro it will spit out 'override' when you want to compile with C++11 and when you don't it does nothing. Not a fan of modern C++ or can't use C++11 for some project, but you can for others? Qt has your back while from your tone wxWidgets forces you to not use the new C++11 features.
- rpwilcox 14y agoMy point was that QT has adopted the new ideas from C++ (like the new override operator), where as wxWidgets (last time I looked, a few years ago) has barely moved to using the STL for containers. wxWidgets is a much more conservative framework, where QT seems to embrace the new stuff (and provide backwards compatible hooks where possible). Of course, you could use different C++ styles and ignore "what you don't like" from either framework, but there's a little impedance mismatch.
- gecko 14y agoI don't quite follow your last point, unless you're mocking wxWidgets. Qt doesn't require you to jump to the C++11 bandwagon, unless you want to. In fact, that post even explicitly highlighted how the old signals and slots will continue to work, and how several of the new Qt macros are no-ops on legacy C++ compilers. Seems like Qt's got your back no matter what your attitude on modern v. older C++.