| … | |
… | |
| 2 | |
2 | |
| 3 | TODO: pack_keys? |
3 | TODO: pack_keys? |
| 4 | TODO: document encode_cbor_sharing? |
4 | TODO: document encode_cbor_sharing? |
| 5 | TODO: weaken cyclic structures? |
5 | TODO: weaken cyclic structures? |
| 6 | TODO: allowed_classes or so? |
6 | TODO: allowed_classes or so? |
|
|
7 | |
|
|
8 | 1.5 |
|
|
9 | - Math::BigFloat madness workaround, see |
|
|
10 | http://blog.schmorp.de/2016-04-23-mathbigfloat-maintainer-fail.html |
|
|
11 | (bugreport by zdm@softvisio.net). |
|
|
12 | - add text_keys and text_strings options to force CBOR text encoding |
|
|
13 | for perl hash keys or all strings, as a result of discussions |
|
|
14 | with Fredrik Ljunggren. |
|
|
15 | - implement support for arbitrary-exponent numbers (see |
|
|
16 | http://peteroupc.github.io/CBOR/bigfrac.html, tags 264 and 265) |
|
|
17 | for both en- and decoding. |
|
|
18 | - implement support for rational numbers (see |
|
|
19 | http://peteroupc.github.io/CBOR/rational.html, tag 30) for both |
|
|
20 | en- and decoding. |
|
|
21 | - this effectively implements all registered CBOR extensions |
|
|
22 | in a sensible manner. |
|
|
23 | - remove some weird dead code that was duplication (%FILTER). |
|
|
24 | - add t/58_hv.t, which tests hashes and the new text_* flags. |
|
|
25 | hashes apparently were not encoded at all in any of the previous |
|
|
26 | tests. |
|
|
27 | - document base-2 Math::BigFloat performance/crash issues. |
|
|
28 | - use stability canary. |
|
|
29 | |
|
|
30 | 1.41 Thu 25 Feb 15:22:03 CET 2016 |
|
|
31 | - avoid perl panics on nested FREEZE/THAW calls (testcase by |
|
|
32 | Victor Efimov). |
| 7 | |
33 | |
| 8 | 1.4 Mon Feb 8 05:10:15 CET 2016 |
34 | 1.4 Mon Feb 8 05:10:15 CET 2016 |
| 9 | - buffer overflow fix: a fast path during decoding did not check |
35 | - buffer overflow fix: a fast path during decoding did not check |
| 10 | remaining length when decoding hash keys, found by fuzzing. |
36 | remaining length when decoding hash keys, found by fuzzing. |
| 11 | This can potentially leak information in the error message |
37 | This can potentially leak information in the error message |
