Il giorno 31/ott/2011, alle ore 10:31, Thiago Macieira ha scritto: > On Monday, 31 de October de 2011 10:23:12 you wrote: >> Thiago Macieira wrote: >>> Sounds interesting to be present and discuss with the Boost developers >>> ways to improve collaboration. Maybe someone will finally convince them >>> to maintain binary compatibility so their libraries could become >>> *actually* useful as part of a larger API... >> >> Can we similarly be convinced to adopt generic programming practices? >> Actually we are... we just keep re-inventing their wheels ;-) >> >> I think the important question is not necessarily binary compatibility. I, >> for one, would love to be able to just *use* Boost inside Qt, in particular >> source-only libraries. As long as we don't touch it in our binary interface >> the lack of BC promise shouldn't affect us. Think TR1 and C++11-features >> available with legacy compilers. >> >> But anyway, that's a big flame-war about to happen ;-) > > The header-only libraries should be usable inside Qt without ill > side-effects. > So I'd say go ahead and use it. Just be mindful that your colleagues may not > know boost as well as you do, so comment your code well :-) > > If you do that, it might be a good idea to import the headers into > src/3rdparty (after proper exceptions are granted under the CLA). At least > until we have a decent configure system to more easily detect the presence / > absence of libraries.
What is the policy on adding new dependencies to the Qt project? To me, it seems a bad idea to add a dependency on any library unless there is a specific use case were it is really necessary. So adding Boost just because it's "cool" (for some definition is cool) doesn't look like a deal. It doesn't help that I specifically dislike Boost, but that's not the subject of this comment. -- Giovanni Bajo :: [email protected] Develer S.r.l. :: http://www.develer.com My Blog: http://giovanni.bajo.it
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
