On 21 Jul 2010, at 14:28, Eric Niebler wrote:
On 7/21/2010 5:00 PM, Robert Ramey wrote:
Ryan Gallagher wrote:
Based upon your messages, it's not clear to me what this "fix" does. Does it make it so that serialization in 1.44 will be able to read binary archives from 1.41 or does it make it so that serialization in 1.44 will be able to read binary archives from 1.42/43? Or somehow both? Is there a trac issue?
I'll recapilate the history in a little more detail.
a) 1.41 - every thing fine b) 1.42 - 17 November 2009? make some fixes to addressess warning messages. This actually exposed some dependence on undefined behaviorj so it was judged a good thing c) These changes broke MPI but this was not noticed at the time. Doug Gregor checked in some changes to the serialization library to address the MPI issue. But this broke compatibility with previous binary_archives. d) 1.43 released I spent a fair amount of time reconciling all the above. This does require a change in archives which derive from binary_?archive. I am sorry about that, but I could find no other way to reconcile all the requirments. as far as I could see, the changes should be small and perhaps trivial since MPI doesn't have support previous versions.
That sentence doesn't parse. I think you're missing a "to" in there. MPI doesn't have "to" support previous versions, presumably because the serialized forms are only traveling across a wire and are never persisted to disk. Is that right? Matthias, is that assumption correct.
Yes