An important part of the saquen library is the division between the compile time modules and the run time modules. This is implemented through object persistence. My current algorithm to save and load is endian-independent, but I'm not sure whether that provides enough platform independence.
Can I rely on the same encodings for signed integers and floating point numbers? How should I represent strings for internationalization?
With these unanswered questions, my persistence algorithms don't fulfill their objectives completely. Does anybody know any resources about this kind of thing? How much of this do I have to worry about for a library?
-D
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
An important part of the saquen library is the division between the compile time modules and the run time modules. This is implemented through object persistence. My current algorithm to save and load is endian-independent, but I'm not sure whether that provides enough platform independence.
Can I rely on the same encodings for signed integers and floating point numbers? How should I represent strings for internationalization?
With these unanswered questions, my persistence algorithms don't fulfill their objectives completely. Does anybody know any resources about this kind of thing? How much of this do I have to worry about for a library?
-D