… | |
… | |
86 | package JSON::XS; |
86 | package JSON::XS; |
87 | |
87 | |
88 | use strict; |
88 | use strict; |
89 | |
89 | |
90 | BEGIN { |
90 | BEGIN { |
91 | our $VERSION = '1.12'; |
91 | our $VERSION = '1.23'; |
92 | our @ISA = qw(Exporter); |
92 | our @ISA = qw(Exporter); |
93 | |
93 | |
94 | our @EXPORT = qw(to_json from_json objToJson jsonToObj); |
94 | our @EXPORT = qw(to_json from_json objToJson jsonToObj); |
95 | require Exporter; |
95 | require Exporter; |
96 | |
96 | |
… | |
… | |
374 | |
374 | |
375 | JSON numbers and strings become simple Perl scalars. JSON arrays become |
375 | JSON numbers and strings become simple Perl scalars. JSON arrays become |
376 | Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes |
376 | Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes |
377 | C<1>, C<false> becomes C<0> and C<null> becomes C<undef>. |
377 | C<1>, C<false> becomes C<0> and C<null> becomes C<undef>. |
378 | |
378 | |
|
|
379 | =item ($perl_scalar, $characters) = $json->decode_prefix ($json_text) |
|
|
380 | |
|
|
381 | This works like the C<decode> method, but instead of raising an exception |
|
|
382 | when there is trailing garbage after the first JSON object, it will |
|
|
383 | silently stop parsing there and return the number of characters consumed |
|
|
384 | so far. |
|
|
385 | |
|
|
386 | This is useful if your JSON texts are not delimited by an outer protocol |
|
|
387 | (which is not the brightest thing to do in the first place) and you need |
|
|
388 | to know where the JSON text ends. |
|
|
389 | |
|
|
390 | JSON::XS->new->decode_prefix ("[1] the tail") |
|
|
391 | => ([], 3) |
|
|
392 | |
379 | =back |
393 | =back |
380 | |
394 | |
381 | |
395 | |
382 | =head1 MAPPING |
396 | =head1 MAPPING |
383 | |
397 | |
… | |
… | |
598 | It seems that JSON::XS is surprisingly fast, as shown in the following |
612 | It seems that JSON::XS is surprisingly fast, as shown in the following |
599 | tables. They have been generated with the help of the C<eg/bench> program |
613 | tables. They have been generated with the help of the C<eg/bench> program |
600 | in the JSON::XS distribution, to make it easy to compare on your own |
614 | in the JSON::XS distribution, to make it easy to compare on your own |
601 | system. |
615 | system. |
602 | |
616 | |
603 | First comes a comparison between various modules using a very short JSON |
617 | First comes a comparison between various modules using a very short |
604 | string: |
618 | single-line JSON string: |
605 | |
619 | |
606 | {"method": "handleMessage", "params": ["user1", "we were just talking"], "id": null} |
620 | {"method": "handleMessage", "params": ["user1", "we were just talking"], \ |
|
|
621 | "id": null, "array":[1,11,234,-5,1e5,1e7, true, false]} |
607 | |
622 | |
608 | It shows the number of encodes/decodes per second (JSON::XS uses the |
623 | It shows the number of encodes/decodes per second (JSON::XS uses the |
609 | functional interface, while JSON::XS/2 uses the OO interface with |
624 | functional interface, while JSON::XS/2 uses the OO interface with |
610 | pretty-printing and hashkey sorting enabled). Higher is better: |
625 | pretty-printing and hashkey sorting enabled). Higher is better: |
611 | |
626 | |
612 | module | encode | decode | |
627 | module | encode | decode | |
613 | -----------|------------|------------| |
628 | -----------|------------|------------| |
614 | JSON | 11488.516 | 7823.035 | |
629 | JSON | 7645.468 | 4208.613 | |
615 | JSON::DWIW | 94708.054 | 129094.260 | |
630 | JSON::DWIW | 68534.379 | 79437.576 | |
616 | JSON::PC | 63884.157 | 128528.212 | |
631 | JSON::PC | 65948.176 | 78251.940 | |
617 | JSON::Syck | 34898.677 | 42096.911 | |
632 | JSON::Syck | 23379.621 | 28416.694 | |
618 | JSON::XS | 654027.064 | 396423.669 | |
633 | JSON::XS | 388361.481 | 199728.762 | |
619 | JSON::XS/2 | 371564.190 | 371725.613 | |
634 | JSON::XS/2 | 218453.333 | 192399.266 | |
|
|
635 | JSON::XS/3 | 338250.323 | 192399.266 | |
|
|
636 | Storable | 15732.573 | 28571.553 | |
620 | -----------+------------+------------+ |
637 | -----------+------------+------------+ |
621 | |
638 | |
622 | That is, JSON::XS is more than six times faster than JSON::DWIW on |
639 | That is, JSON::XS is about five times faster than JSON::DWIW on encoding, |
623 | encoding, more than three times faster on decoding, and about thirty times |
640 | about three times faster on decoding, and over fourty times faster |
624 | faster than JSON, even with pretty-printing and key sorting. |
641 | than JSON, even with pretty-printing and key sorting. It also compares |
|
|
642 | favourably to Storable for small amounts of data. |
625 | |
643 | |
626 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
644 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
627 | search API (http://nanoref.com/yahooapis/mgPdGg): |
645 | search API (http://nanoref.com/yahooapis/mgPdGg): |
628 | |
646 | |
629 | module | encode | decode | |
647 | module | encode | decode | |
630 | -----------|------------|------------| |
648 | -----------|------------|------------| |
631 | JSON | 273.023 | 44.674 | |
649 | JSON | 254.685 | 37.665 | |
632 | JSON::DWIW | 1089.383 | 1145.704 | |
650 | JSON::DWIW | 1014.244 | 1087.678 | |
633 | JSON::PC | 3097.419 | 2393.921 | |
651 | JSON::PC | 3602.116 | 2307.352 | |
634 | JSON::Syck | 514.060 | 843.053 | |
652 | JSON::Syck | 558.035 | 776.263 | |
635 | JSON::XS | 6479.668 | 3636.364 | |
653 | JSON::XS | 5747.196 | 3543.684 | |
636 | JSON::XS/2 | 3774.221 | 3599.124 | |
654 | JSON::XS/2 | 3968.121 | 3589.170 | |
|
|
655 | JSON::XS/3 | 6105.246 | 3561.134 | |
|
|
656 | Storable | 4456.337 | 5320.020 | |
637 | -----------+------------+------------+ |
657 | -----------+------------+------------+ |
638 | |
658 | |
639 | Again, JSON::XS leads by far. |
659 | Again, JSON::XS leads by far. |
640 | |
660 | |
641 | On large strings containing lots of high unicode characters, some modules |
661 | On large strings containing lots of high unicode characters, some modules |