Open GoogleCodeExporter opened 8 years ago
OTextStream is named that way because it e.g. represents the number 255, as
text
('2, '5', and '5'), whereas OBinaryStream would represent it as binary
(0xffffffff).
However, the metadata that SF writes out, to describe what is serialized, are
the
same for both OTextStream and OBinaryStream, and uses binary values, not human
readable characters.
So if you open the output file in a text editor, you should see the actual
values
you serialized in text, but in between them will be non-text characters.
Original comment by jarl.lin...@gmail.com
on 30 Jul 2009 at 9:17
Ah, I expected it to work like boost::archive::text_iarchive.
Anyway, I am successfully using boost serialization for both remote calling and
saving to file, so I am happy :)
Original comment by marius.k...@gmail.com
on 30 Jul 2009 at 9:32
Original comment by jarl.lin...@gmail.com
on 6 Aug 2009 at 12:29
Original issue reported on code.google.com by
marius.k...@gmail.com
on 29 Jul 2009 at 1:11Attachments: