On Sat, Oct 13, 2012 at 10:21 PM, Dave Abrahams <dave@boostpro.com> wrote:
on Fri Oct 12 2012, "Vicente J. Botet Escriba" <vicente.botet-AT-wanadoo.fr> wrote:
Any addition code has its influence on how the library could evolve. I really would prefer to remove these interfaces for Boost 1.56. I think that 1 year and a half is enough time to move to the new interface.
Then I think library decoupling is the right way even more.
You are surely right, but this is not a priority for me. What others think?
In general I'm all for decoupling, but in the case of Chrono I wonder if it's worth the trouble, since it is, after all, standard in C++11. Also, I bet C++03 implementations are going to start shipping with approximations for all the C++11 libraries, if they haven't already.
Decoupling has additional potential of reducing compile times. Currently, including boost/thread/mutex.hpp pulls in a great deal of DateTime and Chrono, even if you don't use any timed functions (which is a typical case).