At this time, unit-specific compile-time conversion constantsĪre used to convert the source unit to the target unit. The only context in which these different types differ is when being converted Each of these units is nothingīut a thin wrapper around a signed integral count. Or waiting to obtain the lock on a mutex. The most common units used when sleeping, waiting on a condition variable, These units were chosen as a subset of the boost library because they are The implementation will eventually work with most C++03 conforming compilers. Thread safe to use a function that modifies the access to a user variable Of exception safety as long as the underlying parameters provide it.Īll functions in the library are thread-unsafe except when noted explicitly.Īs Boost.Chrono doesn't use mutable global variables the thread-safetyĪnalysis is limited to the access to each instance variable. Library you need also to link with the Boost.Systemĭefining BOOST_ERROR_CODE_HEADER_ONLY you will no need to link with itĪs the dependent part is header only then.Īll functions in the library are exception-neutral and provide strong guarantee

In addition to link with the Boost.Chrono Howeverīoost.Chrono depends on the non header-only library Boost.System, so thatīoost.System has an undocumented feature (use of macro BOOST_ERROR_CODE_HEADER_ONLY)ĭefined you need to compile it and build the library before use, for exampleįor is_base, is_convertible, common_type. Library defining BOOST_CHRONO_HEADER_ONLY. The simple way is to decompress (or checkout from SVN) the files in yourīoost.Chrono can be configured as a header-only

Just go to hereĪnd follow the instructions there for anonymous SVN access. Trunk directories boost/chrono and libs/chrono. You can also access the latest (unstable?) state from the Boost Boost.Chrono is in the latest Boost releaseĭocumentation, tests and examples folder are at boost / libs / chrono /.

Quick CPU 4.6.0 for iphone instal