Subject: [boost] [chrono/date] Unit specifiers arithmetic
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2013-05-06 06:31:11
Moving from checked dates to unchecked ones by default and forcing to
user the Unit specifiers year/month/day in any date constructor (even
the unchecked ones) has some ugly consequences. Note that I was able to
build an unchecked date as
date d(2013,5,6, no_check);
the following will not compile now as the constructors expects a year
but y+1 is an int.
date d(y+1, m, d);
The user needs to type
date d(year(y+1), m, d);
Is this what we want to provide to the user or should we add basic
arithmetic on these unit specifiers?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk