18 Sep
2014
18 Sep
'14
3:14 a.m.
On Wednesday 17 September 2014 14:24:28 Robert Ramey wrote:
Stephen Kelly-2 wrote
Robert Ramey wrote:
The "correct" solution to the above is for date-time to build two modules: date-time and date-time-serialization.
Is this "at the expense of everyone who wants to ship datetime with support for serialization in the package"? Is that 'non-obvious' too? Is this a net- positive?
I think its a much smaller number of people.
anyone who explicitly includes date-time/serialization.hpp will know that he has to ship the data-time-serialization.dll.
Just to be closer to reality, serialization support in DateTime is header- only.