I've got the feeling that the particular type of problem demonstrated by my example should be fixable without impacting significantly on performance.
It would; but to what end?
It would very slightly relax the conditions under which Storable could successfully be used as a file interchange format: if both source and destination are: 64-bit; and little-endian; and use the same floating point format; and are using ASCII or utf-8 (eg. not Win-1252) as the internal format for strings; and ...) then you might get away with using binary Storable files as an interchange format.
But would that slight "improvement" as an interchange format be a good thing?
In reply to Re^10: Storable- long integer size
by BrowserUk
in thread Storable- long integer size
by sectokia
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |