|
Boost : |
From: andreas_huber69 (andreas_at_[hidden])
Date: 2001-12-19 01:26:49
> something a touch more complicated needs to be done. In cases where
> there isn't a really good reason not to (e.g. storing a large
amount of
> datetime data contraindicates this practice), I use a
datetime_interval
> even when representing a basic unit of datetime (e.g. December 17,
2001,
> if the resolution is days). I think this keeps my code cleaner.
>
> I don't really know why people don't treat datetime_interval as the
> fundamental abstraction, rather than datetime_instant. Formerly the
> idea of a half-open range might have seemed a bit obscure, but that
> shouldn't be the case for today's C++ programmer.
Sorry, I'm not sure whether I understand. Would you use TWO
datetime_instant objects (or one instant and one span?) to represent
December 17, 2001? What advantage does this have? Please give an
example.
Thanks,
Andreas
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk