[serialization] Observation regarding xml archives and library version

Hi folks, hi Robert, did anyone notice that xml archives can be loaded where other archive types throw an "unsupported version" exception? I was rather surprised when I was able to read in an xml archive created by 1.41 using 1.34! The internal library version changed twice since then, so ... ... are you a magician, Robert? :-) Or is this an undocumented virtue of xml archives? Or is this just a bug nobody seems to have noticed before? Regards, -- Christian Pfligersdorffer Software Engineering http://www.eos.info

Pfligersdorffer, Christian wrote:
Hi folks, hi Robert,
did anyone notice that xml archives can be loaded where other archive types throw an "unsupported version" exception? I was rather surprised when I was able to read in an xml archive created by 1.41 using 1.34! The internal library version changed twice since then, so ...
... are you a magician, Robert? :-) Or is this an undocumented virtue of xml archives? Or is this just a bug nobody seems to have noticed before?
Regards,
I have no explanation. Archives should all act the same so it's likely a bug somewhere. Note that text base archives actually "transform" the data into text an back so it could be that this "transformation" fixes something by accident Robert Ramey
participants (2)
-
Pfligersdorffer, Christian
-
Robert Ramey