Skip to content

0.9.4

Latest
Compare
Choose a tag to compare
@dalehenrich dalehenrich released this 30 Jun 00:35
· 33 commits to gemstone since this release

PR #10 with fix Issue #6:

  • old-style STON (STON[Reader|Writer]) supports which means handicapped handling of multi-byte characters
  • old-style GemStone/tODE support (STON051[Reader|Writer]) where UTF8 encoding is supplied at individual string level and codePoints over 126 are escaped
  • new-style GemStone/TODE support (STON091[Reader|Writer]) where UTF8 encoding is done for the entire STON string, no character escaping is necessary (UTF8uses 8-bit ASCII characters), if escaped characters are encountered, assumption is made that STON was encoded using old-style GemStone/tODE (STON051[Reader|Writer])
  • new-style STON (STONUtd8[Reader|Writer]) support where UTF8 encoding is done for the entire STON string, no character escaping is used and on decode escaped codePoints signal an error ...
  • support both pharo and gemstone on the gemstone branch ...

In support of dalehenrich/tode#175.