| 1 | Revision history for Perl extension JSON::XS |
1 | Revision history for Perl extension JSON::XS |
|
|
2 | |
|
|
3 | TODO: maybe detetc and croak on more invalid inputs (e.g. +-inf/nan) |
|
|
4 | |
|
|
5 | 2.3 Wed Aug 18 01:26:47 CEST 2010 |
|
|
6 | - make sure decoder doesn't change the decoding in the incremental |
|
|
7 | parser (testcase provided by Hendrik Schumacher). |
|
|
8 | - applied patch by DaTa for Data::Dumper support in json_xs. |
|
|
9 | - added -t dump support to json_xs, using Data::Dump. |
|
|
10 | - added -f eval support to json_xs. |
|
|
11 | |
|
|
12 | 2.29 Wed Mar 17 02:39:12 CET 2010 |
|
|
13 | - fix a memory leak when callbacks set using filter_json_object |
|
|
14 | or filter_json_single_key_object were called (great testcase |
|
|
15 | by Eric Wilhelm). |
|
|
16 | |
|
|
17 | 2.28 Thu Mar 11 20:30:46 CET 2010 |
|
|
18 | - implement our own atof function - perl's can be orders of |
|
|
19 | magnitudes slower than even the system one. on the positive |
|
|
20 | side, ours seems to be more exact in general than perl's. |
|
|
21 | (testcase provided by Tim Meadowcroft). |
|
|
22 | - clarify floating point conversion issues a bit. |
|
|
23 | - update jpsykes csrf article url. |
|
|
24 | - updated benchmark section - JSON::PP became much faster! |
|
|
25 | |
|
|
26 | 2.27 Thu Jan 7 07:35:08 CET 2010 |
|
|
27 | - support relaxed option inside the incremental parser |
|
|
28 | (testcase provided by IKEGAMI via Makamaka). |
|
|
29 | |
|
|
30 | 2.26 Sat Oct 10 03:26:19 CEST 2009 |
|
|
31 | - big integers could become truncated (based on patch |
|
|
32 | by Strobl Anton). |
|
|
33 | - output format change: indent now adds a final newline, which is |
|
|
34 | more expected and more true to the documentation. |
|
|
35 | |
|
|
36 | 2.25 Sat Aug 8 12:04:41 CEST 2009 |
|
|
37 | - the perl debugger completely breaks lvalue subs - try to work |
|
|
38 | around the issue. |
|
|
39 | - ignore RMAGICAL hashes w.r.t. CANONICAL. |
|
|
40 | - try to work around a possible char signedness issue on aix. |
|
|
41 | - require common sense. |
|
|
42 | |
|
|
43 | 2.24 Sat May 30 08:25:45 CEST 2009 |
|
|
44 | - the incremental parser did not update its parse offset |
|
|
45 | pointer correctly when parsing utf8-strings (nicely |
|
|
46 | debugged by Martin Evans). |
|
|
47 | - appending a non-utf8-string to the incremental parser |
|
|
48 | in utf8 mode failed to upgrade the string. |
|
|
49 | - wording of parse error messages has been improved. |
|
|
50 | |
|
|
51 | 2.232 Sun Feb 22 11:12:25 CET 2009 |
|
|
52 | - use an exponential algorithm to extend strings, to |
|
|
53 | help platforms with bad or abysmal==windows memory |
|
|
54 | allocater performance, at the expense of some memory |
|
|
55 | wastage (use shrink to recover this extra memory). |
|
|
56 | (nicely analysed by Dmitry Karasik). |
|
|
57 | |
|
|
58 | 2.2311 Thu Feb 19 02:12:54 CET 2009 |
|
|
59 | - add a section "JSON and ECMAscript" to explain some |
|
|
60 | incompatibilities between the two (problem was noted by |
|
|
61 | various people). |
|
|
62 | - add t/20_faihu.t. |
| 2 | |
63 | |
| 3 | 2.231 Thu Nov 20 04:59:08 CET 2008 |
64 | 2.231 Thu Nov 20 04:59:08 CET 2008 |
| 4 | - work around 5.10.0 magic bugs where manipulating magic values |
65 | - work around 5.10.0 magic bugs where manipulating magic values |
| 5 | (such as $1) would permanently damage them as perl would |
66 | (such as $1) would permanently damage them as perl would |
| 6 | ignore the magicalness, by making a full copy of the string, |
67 | ignore the magicalness, by making a full copy of the string, |
| 7 | reported by Dmitry Karasik. |
68 | reported by Dmitry Karasik. |
| 8 | - work around spurious wanrings under older perl 5.8's. |
69 | - work around spurious warnings under older perl 5.8's. |
| 9 | |
70 | |
| 10 | 2.23 Mon Sep 29 05:08:29 CEST 2008 |
71 | 2.23 Mon Sep 29 05:08:29 CEST 2008 |
| 11 | - fix a compilation problem when perl is not using char * as, well, |
72 | - fix a compilation problem when perl is not using char * as, well, |
| 12 | char *. |
73 | char *. |
| 13 | - use PL_hexdigit in favour of rolling our own. |
74 | - use PL_hexdigit in favour of rolling our own. |
