msgpack-perl
msgpack-perl copied to clipboard
msgpack
MessagePack serializer implementation for Perl / msgpack.org[Perl]
Creates new flag, `prefer_float32`, which allows the use of 5 bytes per float, instead of the default 9. Flag is named "prefer_float32" to anticipate this library's move to more recent...
Current prefer_integer treats numbers with leading zero and negative zero as integer. This modifies original data, and unpacked data are not the same as original data any more. This PR...
Currently, unpacking large array-32 can easily leads to OOM. For example, the following one-liner code tries to allocate more than 30 GB but failed with ENOMEM. ``` $ strace perl...
Hello, After a lot of digging, I finally managed to understand why this module in my test script was always assuming that integers were huge float64's. Here's my discovery: ```perl...
Single precision floats defined in msgpack spec, doesn't seem to be implemented here, except during decoding stage. This would save a significant amount of data for our team ~40% of...
This change promotes type compatibility with other CPAN serialization modules like JSON. This is another take at https://github.com/msgpack/msgpack-perl/issues/17 – see also https://github.com/msgpack/msgpack-perl/pull/34 BREAKING CHANGE: removes stringification of true() to "true"...
Could Types::Serialiser::Boolean be used rather than defining Data::MessagePack::Boolean internally? Using and checking for that during conversion would make interoperability with other serialization formats a lot easier. In particular, it would...
Issue #17: Types::Serialiser is useful to support for interoperability with other CPAN serialization modules like JSON. This patch provides that capability in both XS and PP.
I've noticed some odd behavior, which may simply be the way Perl works, but which could be useful for msgpack-perl to take into account. Also, once again I would ask...