#include <Qt/someheader> not portable
staikos at kde.org
Sat Feb 4 13:09:20 GMT 2006
On Saturday 04 February 2006 08:04, Simon Hausmann wrote:
> > The documentation on doc.trolltech.com says "#include <QClassName>",
> > though.
> I think #include <QClassName> is the style we should promote to application
> developers. It's convenient and it does not require one to remember which
> module a certain class is each time one adds an #include statement.
> #include <QtModule/headerfile.h> on the other hand makes sense for
> installed library header files because it means that a user of the header
> file doesn't have to care about having the depending modules in the include
> search path.
You don't think we'll use <QtGui> in the end? Our experience with Qt4 so
far has been that we include so many classes we might as well have included
the wrappers instead.
KDE Developer http://www.kde.org/
Staikos Computing Services Inc. http://www.staikos.net/
More information about the kde-core-devel