| … | |
… | |
| 3 | TODO: maybe detect and croak on more invalid inputs (e.g. +-inf/nan) |
3 | TODO: maybe detect and croak on more invalid inputs (e.g. +-inf/nan) |
| 4 | TODO: maybe avoid the reblessing and better support readonly objects. |
4 | TODO: maybe avoid the reblessing and better support readonly objects. |
| 5 | TODO: how to cope with tagged values and standard json decoders |
5 | TODO: how to cope with tagged values and standard json decoders |
| 6 | TODO: investigate magic (Eric Brine) |
6 | TODO: investigate magic (Eric Brine) |
| 7 | TODO: [PATCH] Types::Serialiser: Inline true(), false() and error() functions |
7 | TODO: [PATCH] Types::Serialiser: Inline true(), false() and error() functions |
|
|
8 | TODO: replace bool_stash by BOOL_STASH seems to work with mod_perl, make a compile time option? |
| 8 | |
9 | |
| 9 | TODO: testcase Wesley Schwengle |
10 | TODO: validate_utf8, apparewntly some people confuse themselves. |
| 10 | 4.02 |
11 | TODO: security considerations |
|
|
12 | |
|
|
13 | 4.03 Tue Oct 27 19:05:01 CET 2020 |
|
|
14 | - when parsing comments in relaxed mode, JSON::XS would detect garbage |
|
|
15 | after the JSON text if the comment is after the end and does not end in |
|
|
16 | a newline (reported by Felipe Gasper). |
|
|
17 | |
|
|
18 | 4.02 Wed Mar 6 08:31:24 CET 2019 |
| 11 | - undo the fix from 4.01, it breaks more things than it fixes. |
19 | - undo the fix from 4.01, it breaks more things than it fixes |
|
|
20 | (another testcase by Wesley Schwengle). |
|
|
21 | - try a proper fix this time. |
| 12 | |
22 | |
| 13 | 4.01 Sun Feb 24 05:03:30 CET 2019 |
23 | 4.01 Sun Feb 24 05:03:30 CET 2019 |
| 14 | - fix some stack corruption caused mostly when calling methods |
24 | - fix some stack corruption caused mostly when calling methods |
| 15 | in list context (tewstcase by Wesley Schwengle). |
25 | in list context (testcase by Wesley Schwengle). |
| 16 | |
26 | |
| 17 | 4.0 Fri Nov 16 00:06:54 CET 2018 |
27 | 4.0 Fri Nov 16 00:06:54 CET 2018 |
| 18 | - SECURITY IMPLICATION: this release enables allow_nonref by default |
28 | - SECURITY IMPLICATION: this release enables allow_nonref by default |
| 19 | for compatibnility with RFC 7159 and newer. See "old" vs. "new" |
29 | for compatibility with RFC 7159 and newer. See "old" vs. "new" |
| 20 | JSON under SECURITY CONSIDERATIONS. |
30 | JSON under SECURITY CONSIDERATIONS. |
| 21 | - reworked the "old" vs. "new" JSON section. |
31 | - reworked the "old" vs. "new" JSON section. |
| 22 | - add ->boolean_values to provide the values to which booleans |
32 | - add ->boolean_values to provide the values to which booleans |
| 23 | decode (requested by Aristotle Pagaltzis). |
33 | decode (requested by Aristotle Pagaltzis). |
| 24 | - decode would wrongly accept ASCII NUL characters instead of |
34 | - decode would wrongly accept ASCII NUL characters instead of |
