From: Pavol Droba (droba_at_[hidden])
Date: 2004-11-22 09:38:42
It seems that there is a bug in the date time documentation
Documentation says this:
To use the alternate resolution (64 bit microsecond) the variable
BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG must be defined in the library users
project files (ie Makefile, Jamfile, etc). This macro is not used by the
Gregorian system and therefore has no effect when building the library."
But in reality, the negation is actualy true. 64bit precision is used when this
macro is NOT defined.
In addition there is a slight problem with posix_time::microseconds() (and possibly with
other similar function as well). Somewhere along the way, parameter is converted to long.
This might cause some problems, since the resolution is larger (64bit).
For instance time_duration::total_microseconds() returns 64bit integer. If the return
value is used to initialize a duration of that lenght, overflow occurs.
I'm using current cvs version of boost.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk