On 2014-06-30, Olivier Goffart <[email protected]> wrote: > Totally off topic: I think using private header should be tried to be > avoided. > In the past, we used private header inside Qt because Qt was not split that > much. But one of the goal of modularisation was to allow independent release > of different component of Qt. The problem is that we could not get rid of > the > private header dependencies at the time (too much work). > But still now, every module, even new, are using the private headers. Nothing > is done to try to prevent it. > > I think there should be some kind of long term goal to avoid using private > headers. > > We need to find a solution so that one need not to inherit from > QObjectPrivate. (There is already QObject::setUserData, but it could be done > better i guess) > > We need also to identify private APIs that could be polished and made public. > For some modules such as QtQuick this is probably too hard. > But for new modules such as WebEngine or such, it may be possible to avoid > dependency on private API.
*applause* /Sune _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
