… | |
… | |
83 | this module usually compares favourably in terms of speed, too. |
83 | this module usually compares favourably in terms of speed, too. |
84 | |
84 | |
85 | =item * simple to use |
85 | =item * simple to use |
86 | |
86 | |
87 | This module has both a simple functional interface as well as an object |
87 | This module has both a simple functional interface as well as an object |
88 | oriented interface interface. |
88 | oriented interface. |
89 | |
89 | |
90 | =item * reasonably versatile output formats |
90 | =item * reasonably versatile output formats |
91 | |
91 | |
92 | You can choose between the most compact guaranteed-single-line format |
92 | You can choose between the most compact guaranteed-single-line format |
93 | possible (nice for simple line-based protocols), a pure-ASCII format |
93 | possible (nice for simple line-based protocols), a pure-ASCII format |
… | |
… | |
101 | |
101 | |
102 | package JSON::XS; |
102 | package JSON::XS; |
103 | |
103 | |
104 | use common::sense; |
104 | use common::sense; |
105 | |
105 | |
106 | our $VERSION = '2.3'; |
106 | our $VERSION = 2.34; |
107 | our @ISA = qw(Exporter); |
107 | our @ISA = qw(Exporter); |
108 | |
108 | |
109 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
109 | our @EXPORT = qw(encode_json decode_json); |
110 | |
|
|
111 | sub to_json($) { |
|
|
112 | require Carp; |
|
|
113 | Carp::croak ("JSON::XS::to_json has been renamed to encode_json, either downgrade to pre-2.0 versions of JSON::XS or rename the call"); |
|
|
114 | } |
|
|
115 | |
|
|
116 | sub from_json($) { |
|
|
117 | require Carp; |
|
|
118 | Carp::croak ("JSON::XS::from_json has been renamed to decode_json, either downgrade to pre-2.0 versions of JSON::XS or rename the call"); |
|
|
119 | } |
|
|
120 | |
110 | |
121 | use Exporter; |
111 | use Exporter; |
122 | use XSLoader; |
112 | use XSLoader; |
123 | |
113 | |
124 | =head1 FUNCTIONAL INTERFACE |
114 | =head1 FUNCTIONAL INTERFACE |
… | |
… | |
432 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
422 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
433 | by sorting their keys. This is adding a comparatively high overhead. |
423 | by sorting their keys. This is adding a comparatively high overhead. |
434 | |
424 | |
435 | If C<$enable> is false, then the C<encode> method will output key-value |
425 | If C<$enable> is false, then the C<encode> method will output key-value |
436 | pairs in the order Perl stores them (which will likely change between runs |
426 | pairs in the order Perl stores them (which will likely change between runs |
437 | of the same script). |
427 | of the same script, and can change even within the same run from 5.18 |
|
|
428 | onwards). |
438 | |
429 | |
439 | This option is useful if you want the same data structure to be encoded as |
430 | This option is useful if you want the same data structure to be encoded as |
440 | the same JSON text (given the same overall settings). If it is disabled, |
431 | the same JSON text (given the same overall settings). If it is disabled, |
441 | the same hash might be encoded differently even if contains the same data, |
432 | the same hash might be encoded differently even if contains the same data, |
442 | as key-value pairs have no inherent ordering in Perl. |
433 | as key-value pairs have no inherent ordering in Perl. |
… | |
… | |
666 | |
657 | |
667 | See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
658 | See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
668 | |
659 | |
669 | =item $json_text = $json->encode ($perl_scalar) |
660 | =item $json_text = $json->encode ($perl_scalar) |
670 | |
661 | |
671 | Converts the given Perl data structure (a simple scalar or a reference |
662 | Converts the given Perl value or data structure to its JSON |
672 | to a hash or array) to its JSON representation. Simple scalars will be |
663 | representation. Croaks on error. |
673 | converted into JSON string or number sequences, while references to arrays |
|
|
674 | become JSON arrays and references to hashes become JSON objects. Undefined |
|
|
675 | Perl values (e.g. C<undef>) become JSON C<null> values. Neither C<true> |
|
|
676 | nor C<false> values will be generated. |
|
|
677 | |
664 | |
678 | =item $perl_scalar = $json->decode ($json_text) |
665 | =item $perl_scalar = $json->decode ($json_text) |
679 | |
666 | |
680 | The opposite of C<encode>: expects a JSON text and tries to parse it, |
667 | The opposite of C<encode>: expects a JSON text and tries to parse it, |
681 | returning the resulting simple scalar or reference. Croaks on error. |
668 | returning the resulting simple scalar or reference. Croaks on error. |
682 | |
|
|
683 | JSON numbers and strings become simple Perl scalars. JSON arrays become |
|
|
684 | Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes |
|
|
685 | C<1>, C<false> becomes C<0> and C<null> becomes C<undef>. |
|
|
686 | |
669 | |
687 | =item ($perl_scalar, $characters) = $json->decode_prefix ($json_text) |
670 | =item ($perl_scalar, $characters) = $json->decode_prefix ($json_text) |
688 | |
671 | |
689 | This works like the C<decode> method, but instead of raising an exception |
672 | This works like the C<decode> method, but instead of raising an exception |
690 | when there is trailing garbage after the first JSON object, it will |
673 | when there is trailing garbage after the first JSON object, it will |
691 | silently stop parsing there and return the number of characters consumed |
674 | silently stop parsing there and return the number of characters consumed |
692 | so far. |
675 | so far. |
693 | |
676 | |
694 | This is useful if your JSON texts are not delimited by an outer protocol |
677 | This is useful if your JSON texts are not delimited by an outer protocol |
695 | (which is not the brightest thing to do in the first place) and you need |
|
|
696 | to know where the JSON text ends. |
678 | and you need to know where the JSON text ends. |
697 | |
679 | |
698 | JSON::XS->new->decode_prefix ("[1] the tail") |
680 | JSON::XS->new->decode_prefix ("[1] the tail") |
699 | => ([], 3) |
681 | => ([], 3) |
700 | |
682 | |
701 | =back |
683 | =back |
… | |
… | |
740 | |
722 | |
741 | If the method is called in scalar context, then it will try to extract |
723 | If the method is called in scalar context, then it will try to extract |
742 | exactly I<one> JSON object. If that is successful, it will return this |
724 | exactly I<one> JSON object. If that is successful, it will return this |
743 | object, otherwise it will return C<undef>. If there is a parse error, |
725 | object, otherwise it will return C<undef>. If there is a parse error, |
744 | this method will croak just as C<decode> would do (one can then use |
726 | this method will croak just as C<decode> would do (one can then use |
745 | C<incr_skip> to skip the errornous part). This is the most common way of |
727 | C<incr_skip> to skip the erroneous part). This is the most common way of |
746 | using the method. |
728 | using the method. |
747 | |
729 | |
748 | And finally, in list context, it will try to extract as many objects |
730 | And finally, in list context, it will try to extract as many objects |
749 | from the stream as it can find and return them, or the empty list |
731 | from the stream as it can find and return them, or the empty list |
750 | otherwise. For this to work, there must be no separators between the JSON |
732 | otherwise. For this to work, there must be no separators between the JSON |
… | |
… | |
779 | C<incr_parse> died, in which case the input buffer and incremental parser |
761 | C<incr_parse> died, in which case the input buffer and incremental parser |
780 | state is left unchanged, to skip the text parsed so far and to reset the |
762 | state is left unchanged, to skip the text parsed so far and to reset the |
781 | parse state. |
763 | parse state. |
782 | |
764 | |
783 | The difference to C<incr_reset> is that only text until the parse error |
765 | The difference to C<incr_reset> is that only text until the parse error |
784 | occured is removed. |
766 | occurred is removed. |
785 | |
767 | |
786 | =item $json->incr_reset |
768 | =item $json->incr_reset |
787 | |
769 | |
788 | This completely resets the incremental parser, that is, after this call, |
770 | This completely resets the incremental parser, that is, after this call, |
789 | it will be as if the parser had never parsed anything. |
771 | it will be as if the parser had never parsed anything. |
… | |
… | |
795 | =back |
777 | =back |
796 | |
778 | |
797 | =head2 LIMITATIONS |
779 | =head2 LIMITATIONS |
798 | |
780 | |
799 | All options that affect decoding are supported, except |
781 | All options that affect decoding are supported, except |
800 | C<allow_nonref>. The reason for this is that it cannot be made to |
782 | C<allow_nonref>. The reason for this is that it cannot be made to work |
801 | work sensibly: JSON objects and arrays are self-delimited, i.e. you can concatenate |
783 | sensibly: JSON objects and arrays are self-delimited, i.e. you can |
802 | them back to back and still decode them perfectly. This does not hold true |
784 | concatenate them back to back and still decode them perfectly. This does |
803 | for JSON numbers, however. |
785 | not hold true for JSON numbers, however. |
804 | |
786 | |
805 | For example, is the string C<1> a single JSON number, or is it simply the |
787 | For example, is the string C<1> a single JSON number, or is it simply the |
806 | start of C<12>? Or is C<12> a single JSON number, or the concatenation |
788 | start of C<12>? Or is C<12> a single JSON number, or the concatenation |
807 | of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS |
789 | of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS |
808 | takes the conservative route and disallows this case. |
790 | takes the conservative route and disallows this case. |
… | |
… | |
987 | If the number consists of digits only, JSON::XS will try to represent |
969 | If the number consists of digits only, JSON::XS will try to represent |
988 | it as an integer value. If that fails, it will try to represent it as |
970 | it as an integer value. If that fails, it will try to represent it as |
989 | a numeric (floating point) value if that is possible without loss of |
971 | a numeric (floating point) value if that is possible without loss of |
990 | precision. Otherwise it will preserve the number as a string value (in |
972 | precision. Otherwise it will preserve the number as a string value (in |
991 | which case you lose roundtripping ability, as the JSON number will be |
973 | which case you lose roundtripping ability, as the JSON number will be |
992 | re-encoded toa JSON string). |
974 | re-encoded to a JSON string). |
993 | |
975 | |
994 | Numbers containing a fractional or exponential part will always be |
976 | Numbers containing a fractional or exponential part will always be |
995 | represented as numeric (floating point) values, possibly at a loss of |
977 | represented as numeric (floating point) values, possibly at a loss of |
996 | precision (in which case you might lose perfect roundtripping ability, but |
978 | precision (in which case you might lose perfect roundtripping ability, but |
997 | the JSON number will still be re-encoded as a JSON number). |
979 | the JSON number will still be re-encoded as a JSON number). |
998 | |
980 | |
999 | Note that precision is not accuracy - binary floating point values cannot |
981 | Note that precision is not accuracy - binary floating point values cannot |
1000 | represent most decimal fractions exactly, and when converting from and to |
982 | represent most decimal fractions exactly, and when converting from and to |
1001 | floating point, JSON::XS only guarantees precision up to but not including |
983 | floating point, JSON::XS only guarantees precision up to but not including |
1002 | the leats significant bit. |
984 | the least significant bit. |
1003 | |
985 | |
1004 | =item true, false |
986 | =item true, false |
1005 | |
987 | |
1006 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
988 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
1007 | respectively. They are overloaded to act almost exactly like the numbers |
989 | respectively. They are overloaded to act almost exactly like the numbers |
… | |
… | |
1023 | |
1005 | |
1024 | =over 4 |
1006 | =over 4 |
1025 | |
1007 | |
1026 | =item hash references |
1008 | =item hash references |
1027 | |
1009 | |
1028 | Perl hash references become JSON objects. As there is no inherent ordering |
1010 | Perl hash references become JSON objects. As there is no inherent |
1029 | in hash keys (or JSON objects), they will usually be encoded in a |
1011 | ordering in hash keys (or JSON objects), they will usually be encoded |
1030 | pseudo-random order that can change between runs of the same program but |
1012 | in a pseudo-random order. JSON::XS can optionally sort the hash keys |
1031 | stays generally the same within a single run of a program. JSON::XS can |
1013 | (determined by the I<canonical> flag), so the same datastructure will |
1032 | optionally sort the hash keys (determined by the I<canonical> flag), so |
1014 | serialise to the same JSON text (given same settings and version of |
1033 | the same datastructure will serialise to the same JSON text (given same |
1015 | JSON::XS), but this incurs a runtime overhead and is only rarely useful, |
1034 | settings and version of JSON::XS), but this incurs a runtime overhead |
1016 | e.g. when you want to compare some JSON text against another for equality. |
1035 | and is only rarely useful, e.g. when you want to compare some JSON text |
|
|
1036 | against another for equality. |
|
|
1037 | |
1017 | |
1038 | =item array references |
1018 | =item array references |
1039 | |
1019 | |
1040 | Perl array references become JSON arrays. |
1020 | Perl array references become JSON arrays. |
1041 | |
1021 | |
… | |
… | |
1137 | =item C<utf8> flag disabled |
1117 | =item C<utf8> flag disabled |
1138 | |
1118 | |
1139 | When C<utf8> is disabled (the default), then C<encode>/C<decode> generate |
1119 | When C<utf8> is disabled (the default), then C<encode>/C<decode> generate |
1140 | and expect Unicode strings, that is, characters with high ordinal Unicode |
1120 | and expect Unicode strings, that is, characters with high ordinal Unicode |
1141 | values (> 255) will be encoded as such characters, and likewise such |
1121 | values (> 255) will be encoded as such characters, and likewise such |
1142 | characters are decoded as-is, no canges to them will be done, except |
1122 | characters are decoded as-is, no changes to them will be done, except |
1143 | "(re-)interpreting" them as Unicode codepoints or Unicode characters, |
1123 | "(re-)interpreting" them as Unicode codepoints or Unicode characters, |
1144 | respectively (to Perl, these are the same thing in strings unless you do |
1124 | respectively (to Perl, these are the same thing in strings unless you do |
1145 | funny/weird/dumb stuff). |
1125 | funny/weird/dumb stuff). |
1146 | |
1126 | |
1147 | This is useful when you want to do the encoding yourself (e.g. when you |
1127 | This is useful when you want to do the encoding yourself (e.g. when you |
… | |
… | |
1263 | output for these property strings, e.g.: |
1243 | output for these property strings, e.g.: |
1264 | |
1244 | |
1265 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
1245 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
1266 | |
1246 | |
1267 | This works because C<__proto__> is not valid outside of strings, so every |
1247 | This works because C<__proto__> is not valid outside of strings, so every |
1268 | occurence of C<"__proto__"\s*:> must be a string used as property name. |
1248 | occurrence of C<"__proto__"\s*:> must be a string used as property name. |
1269 | |
1249 | |
1270 | If you know of other incompatibilities, please let me know. |
1250 | If you know of other incompatibilities, please let me know. |
1271 | |
1251 | |
1272 | |
1252 | |
1273 | =head2 JSON and YAML |
1253 | =head2 JSON and YAML |
… | |
… | |
1445 | process simulations - use fork, it's I<much> faster, cheaper, better). |
1425 | process simulations - use fork, it's I<much> faster, cheaper, better). |
1446 | |
1426 | |
1447 | (It might actually work, but you have been warned). |
1427 | (It might actually work, but you have been warned). |
1448 | |
1428 | |
1449 | |
1429 | |
|
|
1430 | =head1 THE PERILS OF SETLOCALE |
|
|
1431 | |
|
|
1432 | Sometimes people avoid the Perl locale support and directly call the |
|
|
1433 | system's setlocale function with C<LC_ALL>. |
|
|
1434 | |
|
|
1435 | This breaks both perl and modules such as JSON::XS, as stringification of |
|
|
1436 | numbers no longer works correctly (e.g. C<$x = 0.1; print "$x"+1> might |
|
|
1437 | print C<1>, and JSON::XS might output illegal JSON as JSON::XS relies on |
|
|
1438 | perl to stringify numbers). |
|
|
1439 | |
|
|
1440 | The solution is simple: don't call C<setlocale>, or use it for only those |
|
|
1441 | categories you need, such as C<LC_MESSAGES> or C<LC_CTYPE>. |
|
|
1442 | |
|
|
1443 | If you need C<LC_NUMERIC>, you should enable it only around the code that |
|
|
1444 | actually needs it (avoiding stringification of numbers), and restore it |
|
|
1445 | afterwards. |
|
|
1446 | |
|
|
1447 | |
1450 | =head1 BUGS |
1448 | =head1 BUGS |
1451 | |
1449 | |
1452 | While the goal of this module is to be correct, that unfortunately does |
1450 | While the goal of this module is to be correct, that unfortunately does |
1453 | not mean it's bug-free, only that I think its design is bug-free. If you |
1451 | not mean it's bug-free, only that I think its design is bug-free. If you |
1454 | keep reporting bugs they will be fixed swiftly, though. |
1452 | keep reporting bugs they will be fixed swiftly, though. |