Nikolay Mladenov wrote:
On Fri, May 11, 2012 at 2:06 AM, Robert Ramey <ramey@rrsd.com> wrote:
Your right about this and your proposal is a worthy one though I think there's a simpler way to do it.. I'll look into this.
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.
I am not sure how to understand this. The commented out code checks for future versions, not for previous versions?
Robert Ramey
Thanks in advance,
Nikolay Mladenov Sitius Automation Inc.
If I am to avoid the crash when reading future version I seem to have 2 options: 1) add a check in every load/serialize function and throw when future version is detected 2) add the same check but in the fuction or functions that call the load/serialize functions
3) just re-enable the check by chaning the 0 to 1 and rebuild the library. would this not work for you? Robert Ramey
And my problem with 2 is that I have to mess up with the serialization library which I am not so familiar with.
Nikolay Mladenov Sitius Automation Inc.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost