On Thursday, June 11, 2015 11:49:23 AM Marc Mutz wrote: > On Wednesday 10 June 2015 21:03:32 Stephen Kelly wrote: > > I would encourage a discussion of why this module needs namespaces when > > the rest of Qt gets by without them. There is certainly a consistency > > angle. > > I think you come a few years late :)
Not when it comes to public API AFAICS. > QtPatternist An internal namespace, not reflected in the public API. > QtConcurrent A namespace for functions only, no public classes within. > QTest A namespace for functions only, no public classes within. > QV4 An internal namespace, not reflected in the public API. > QtQml An internal namespace, not reflected in the public API. > QtDeclarative I don't see this as a public API namespace neither. Where did you find it? > QtWayland > ... The client module doesn't have public API and the compositor module doesn't use namespaces for the public API. Simon _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
