You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Create a binary stream in a 32 bit architecture machine using some types
that depend on it (e.g. size_t.)
2. Send that stream to a 64 bit machine and attempt to read it.
3. Exceptions will be raised because of unsufficient stream size. Actually, the
whole stream can't be read due to the fact that the 64 bit architecture is
expecting 64 bit size_t data, etc.
We need to have serialized objects be able to be read from machines with other
architectures than the one that serialized the object.
Original issue reported on code.google.com by billybiset on 30 Aug 2011 at 2:54
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
billybiset
on 30 Aug 2011 at 2:54The text was updated successfully, but these errors were encountered: