Subject: Re: [boost] [serialization] Reading newer archives - was throwing unsupported_class_version, now crashes
From: Lars Viklund (zao_at_[hidden])
Date: 2012-05-11 03:33:16
On Thu, May 10, 2012 at 10:06:42PM -0800, Robert Ramey wrote:
> Nikolay Mladenov wrote:
> As to why it's this way, the answer is pretty simple. The original
> version of the library has some errors. Problem is, fixing them
> is much harder than with other libraries because of the requirement
> to maintain the ability to read archives created with previous versions.
This is not an answer. Why was this code defined out, and what is solved
by doing so?
What _is_ the underlying problem, there is nothing in your message that
explains why this happens. No-one goes around and disables code blocks
for no reason, removing functionality.
I cannot trust a library that has secret known bugs, especially if it
has a track record of messing up (like the forgotten version bump and
-- Lars Viklund | zao_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk