> > That's not what I was talking about. Take the example that QIODevice > derives > from QObject. In order to derive from QObject, the qiodevice.h header > needs to > include the full "qobject" headers -- that includes what moc generated > too. So > in order for moc to run on qiodevice.h, it needs to be run first on > qobject.h. > And moc needs to understand whatever it produced too. >
Indeed, this is really a big problem, moc would have to check dependencies. > I don't want to shoot you down without listening to your ideas. I'd like > to > give you a chance to present them and prove them. So if you feel this > strongly > about the feature, go ahead and create a proof of concept. > > I've only said I don't like the idea of installed generated headers, > especially if they are for almost every single class. But if the > advantages > that you are proposing are worth it, we should use it. > > In other words, if you want to see this, you need to create the proof of > concept, prove the 8 points I outlined in the other email and prove to us > that > this is worth the hassle. > > -- > Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org > Software Architect - Intel Open Source Technology Center > PGP/GPG: 0x6EF45358; fingerprint: > E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
