e26fd2ed98
* Synchronize each miscrosec test to the next second (#109) * Synchronize each miscrosec test to the next second The aim is to avoid false positives in test_microsec when the seconds, minutes or hours change during time read between the second_clock and the microsec_clock. * Improved readability of the microcec_time_clock test * Improve performance of adding and subtracting time durations from a ptime. (#99) Modifying ptime objects by adding and subtracting time durations was inefficient because it extracted the date and time of day and then re-constructed a ptime using the date and modified time of day. This can be avoided by using the existing time_system utilities which perform the operation by adjusting the number of ticks. Performance is improved by a factor of 48 on my system. * Update CI Scripts * Add time_duration helper functions: (#113) 1. is_positive() - Return boolean value to indicate whether or not time duration is positive. 2. is_zero() - Return boolean value to indicate whether or not time duration is zero. 3. abs() - Return a time_duration which is the absolute value of time duration. Added documentation for these helper functions and improved existing documentation to indicate constness, return values or static functions. * Cease dependence on MPL (#115) |
||
---|---|---|
build | ||
data | ||
doc | ||
example | ||
include/boost | ||
meta | ||
src | ||
test | ||
xmldoc | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
appveyor.yml | ||
index.html | ||
Jamfile | ||
LICENSE | ||
README.md |
DateTime, part of the collection of Boost C++ Libraries, makes programming with dates and times as simple and natural as programming with strings and integers.
License
Distributed under the Boost Software License, Version 1.0.
Properties
- C++03
- Requires Linking
Build Status
Branch | Travis | Appveyor | Coverity Scan | codecov.io | Deps | Docs | Tests |
---|---|---|---|---|---|---|---|
master |
|||||||
develop |
Directories
Name | Purpose |
---|---|
build |
build script for link library |
data |
timezone database |
doc |
documentation |
example |
use case examples |
include |
headers |
src |
source code for link library |
test |
unit tests |
xmldoc |
additional documentation |
More information
- Ask questions: Be sure to read the documentation first to see if it answers your question.
- Report bugs: Be sure to mention Boost version, platform and compiler you're using. A small compilable code sample to reproduce the problem is always good as well.
- Submit Pull Requests against the develop branch. Note that by submitting patches you agree to license your modifications under the Boost Software License, Version 1.0. Be sure to include tests proving your changes work properly.
- Discussions about the library are held on the Boost developers mailing list. Be sure to read the discussion policy before posting and add the
[date_time]
tag at the beginning of the subject line.