Eric Niebler <eric <at> boostpro.com> writes:
On 7/21/2010 5:00 PM, Robert Ramey wrote:
I hope that clarifies things.
Not quite there yet. You didn't answer Ryan's questions directly. Let me see if I can:
Thanks!
Based upon your messages, it's not clear to me what this "fix" does.
It makes binary archives distinguishable from their incompatible pre-1.42 variants. It provides a standalone utility to help users fix their broken binary archives from 1.42 and 1.43.
So this utility adds in the proper library version number to the archive, right?
It requires users that inherit from a binary archive to manually fix their code. It (does/does not?) help users identify these places in their code.
Thanks for the explanation. At least in my case I don't think I'll need to worry about this.
Does it make it so that serialization in 1.44 will be able to read binary archives from 1.41
Yes(?)
Good. =)
or does it make it so that serialization in 1.44 will be able to read binary archives from 1.42/43?
No.
Sure, but if we have run the aforementioned utility to fix the archives from 1.42/43 then 1.44 will be able to read these, right? Alternatively, if we had the required patch applied to 1.43 before writing our archives then 1.44+ would be able to read them. As I am just looking to start using 1.43 I could still patch the source. This patch can be made available, right? Daniel's suggestion of a point release with this patch applied would be great, but a patch is sufficient for me at least.
Or somehow both? Is there a trac issue?
No(?)
Unless one patched 1.43 first. Perhaps we should create a trac issue and put the patch there. It seems that a late coming "fix" like this should be required to have a trac issues associated with it as well. (I do agree that this is like an oil spill and should be capped asap.) Thanks Eric and Robert! -Ryan