binary archives are implemented to be as fast as possible. There isn't any checking which would impact erformance. One thing that I've found useful is to check the serialization using xml archives. Since these have "end" tags, mis-matched saved/load functions can be detected. This is much harder in other archives. Robert Ramey "Christoph" <christoph.duelli@gmx.de> wrote in message news:fgcl3s$2fp$1@ger.gmane.org... I am experimenting with Boost.Serialization. I tried to de-serialize a (binary) file written for a *different* class. Obviously, this can not work. However, there is not thrown an exception. Question: (How) can I determine that the reading failed? (In case of corrupted or non-matching archives.) (I have attached a small demo.) Best regards Christoph --------------------------------------------------------------------------------
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users