-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
posix_time's no longer boost::serialize between boost v1.64 and v1.65, 1.66 #56
Comments
Yes, this is caused by #35. I'm looking into it. Boost.Serialization has versioning capabilities that could allow for compatibility, except that 1.65 an 1.66 will be writing the same version, so it's now "a mess". |
jeking3
added a commit
to jeking3/date_time
that referenced
this issue
Dec 23, 2017
jeking3
added a commit
to jeking3/date_time
that referenced
this issue
Dec 23, 2017
jeking3
added a commit
to jeking3/date_time
that referenced
this issue
Dec 24, 2017
jeking3
added a commit
to jeking3/date_time
that referenced
this issue
Dec 26, 2017
jeking3
added a commit
to jeking3/date_time
that referenced
this issue
Dec 30, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that
4543: fix ptime 2038 issue
has changed the behavior of boost::serialization. My archives (built with boost 1.64) using boost::serialization (inherently using time_serialization.hpp) no longer load because the hours, minutes, etc fields are now 8 bytes instead of 4 bytes.
I'm using VS2017 15.4 and 15.2
The text was updated successfully, but these errors were encountered: