SMUELLER / Sereal-Decoder-0.13 / Changes 
Revision history for Perl extension Sereal-Decoder

0.01  Tue Aug  8 17:09 2012
  - original version; internal release.

0.02  Tue Aug  8 17:09 2012
  - internal release.

0.03  Tue Sep  4 17:09 2012
  - internal release.

0.04  Thu Sep  6 16:00 2012
  - internal release.

0.05  Fri Sep  7 14:00 2012
  - internal release.

0.06  Mon Sep 10 11:00 2012
  - First public release (CPAN).
  - Beta quality software.

0.07  Tue Sep 11 14:00 2012
  - Improved robustness to bad input data.
  - Test fixes for threaded perls (likely working around a bug in Perl)
  - Improved documentation.

0.08  Thu Sep 13 17:00 2012
  - Documentation fixes
  - Better tests

0.09  Fri Sep 14 09:40 2012
  - Removes use of variadic macros for compatibility with inferior
    compilers.
  - "looks_like_sereal" method/function for a quick way to check for
    valid Sereal *headers*.
  - More liberal set of encoder versions we run the full tests with.

0.10  Mon Sep 17 13:40 20120
  - New 'refuse_objects' option causes the decoder to throw an
    exception when encountering objects in the input data.
    See the "ROBUSTNESS" section in the documentation for why that
    is a good idea.
  - Fixes to error messages.
  - Compiler warning fixes.

0.11  Tue Sep 18 13:00 2012
  - 5.8.5 fixes.
  - Fixes to other languages' reference data output.

0.12 - unreleased

0.13  Tue Oct  2 15:00 2012
  * Important bug fix, important gotcha! *
  - Work around bug in perls <= 5.8.8:
      Multiple references to the same object that has overloading were
      dropping overloadedness on the second and following occurrence.
    => The work-around for this old perl bug means that we have to
       bless objects as we find them during deserialization. By default,
       on newer perls, we only do the bless()ing once after being done
       with serialization. We normally do this for security reasons
       (destructors!). This means that for perls <= 5.8.8, we necessarily
       have the same (very limited) security problem that Storable has
       at all times. Sucks, but better to have it working on 5.8.8 at all.
    => For newer perls, we DO NOT have that security problem!
    => The work-around also slows down operation on 5.8.8 and older. Keep
       that in mind when comparing serialization techniques. Thank you.