You could, or you could just not call these functions and maybe include an "assert" in case you do it by accident. Robert Ramey Peter S. wrote:
ok, in this case, I have some additional questions:
I'm trying to write (well, I haven't even started yet to be honest because I feel like I have to understand the library first) an archive that writes to a (sql) database backend... Now you can't just append some binary data to a database table, so the save/load_binary methods would not work very well here. Is it safe to just define them to do nothing?
This function does exactly what it says. It appends/retrieves raw data to/from the archive.
This can be used for various purpose. Here are some examples.
a) binary_archive implements the serialization of primitive types through this interface. b) suppose you retrieved some binary data from source - like an image in a format you don't care about - and wanted to store it in archive to be retrieved later. You could load/save binary to do this.
Robert Ramey
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users