15 Mar
2011
15 Mar
'11
8:56 p.m.
2011/3/15 Vicente Botet <vicente.botet@wanadoo.fr>:
Joachim Faulhaber wrote:
2011/3/15 Vicente Botet <vicente.botet@wanadoo.fr>:
In any case all the added functions should be accessible only if BOOST_CHRONO_EXTENSIONS is defined, so semantic compatibility with std::chrono is maintained.
Is std::chrono already accepted and frozen in the new standard?
It is accepted, and if I'm not wrong next week will be the next meeting for the C++ standard group, and I suspect that it should be the last one before the next c++0x is accepted. I guess that only bugs corrections are accepted now :(
This is unfortunate, since I intended to challenge its design fundamentally (just kidding) :-D