… | |
… | |
64 | so, and even documents what "correct" means. |
64 | so, and even documents what "correct" means. |
65 | |
65 | |
66 | =item * round-trip integrity |
66 | =item * round-trip integrity |
67 | |
67 | |
68 | When you serialise a perl data structure using only data types supported |
68 | When you serialise a perl data structure using only data types supported |
69 | by JSON, the deserialised data structure is identical on the Perl level. |
69 | by JSON and Perl, the deserialised data structure is identical on the Perl |
70 | (e.g. the string "2.0" doesn't suddenly become "2" just because it looks |
70 | level. (e.g. the string "2.0" doesn't suddenly become "2" just because |
71 | like a number). There minor I<are> exceptions to this, read the MAPPING |
71 | it looks like a number). There I<are> minor exceptions to this, read the |
72 | section below to learn about those. |
72 | MAPPING section below to learn about those. |
73 | |
73 | |
74 | =item * strict checking of JSON correctness |
74 | =item * strict checking of JSON correctness |
75 | |
75 | |
76 | There is no guessing, no generating of illegal JSON texts by default, |
76 | There is no guessing, no generating of illegal JSON texts by default, |
77 | and only JSON is accepted as input by default (the latter is a security |
77 | and only JSON is accepted as input by default (the latter is a security |
… | |
… | |
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.24'; |
106 | our $VERSION = '3.0'; |
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; |
|
|
113 | |
|
|
114 | use Types::Serialiser (); |
123 | |
115 | |
124 | =head1 FUNCTIONAL INTERFACE |
116 | =head1 FUNCTIONAL INTERFACE |
125 | |
117 | |
126 | The following convenience methods are provided by this module. They are |
118 | The following convenience methods are provided by this module. They are |
127 | exported by default: |
119 | exported by default: |
… | |
… | |
148 | This function call is functionally identical to: |
140 | This function call is functionally identical to: |
149 | |
141 | |
150 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
142 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
151 | |
143 | |
152 | Except being faster. |
144 | Except being faster. |
153 | |
|
|
154 | =item $is_boolean = JSON::XS::is_bool $scalar |
|
|
155 | |
|
|
156 | Returns true if the passed scalar represents either JSON::XS::true or |
|
|
157 | JSON::XS::false, two constants that act like C<1> and C<0>, respectively |
|
|
158 | and are used to represent JSON C<true> and C<false> values in Perl. |
|
|
159 | |
|
|
160 | See MAPPING, below, for more information on how JSON values are mapped to |
|
|
161 | Perl. |
|
|
162 | |
145 | |
163 | =back |
146 | =back |
164 | |
147 | |
165 | |
148 | |
166 | =head1 A FEW NOTES ON UNICODE AND PERL |
149 | =head1 A FEW NOTES ON UNICODE AND PERL |
… | |
… | |
432 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
415 | 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. |
416 | by sorting their keys. This is adding a comparatively high overhead. |
434 | |
417 | |
435 | If C<$enable> is false, then the C<encode> method will output key-value |
418 | 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 |
419 | pairs in the order Perl stores them (which will likely change between runs |
437 | of the same script). |
420 | of the same script, and can change even within the same run from 5.18 |
|
|
421 | onwards). |
438 | |
422 | |
439 | This option is useful if you want the same data structure to be encoded as |
423 | 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, |
424 | 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, |
425 | the same hash might be encoded differently even if contains the same data, |
442 | as key-value pairs have no inherent ordering in Perl. |
426 | as key-value pairs have no inherent ordering in Perl. |
… | |
… | |
483 | |
467 | |
484 | =item $json = $json->allow_blessed ([$enable]) |
468 | =item $json = $json->allow_blessed ([$enable]) |
485 | |
469 | |
486 | =item $enabled = $json->get_allow_blessed |
470 | =item $enabled = $json->get_allow_blessed |
487 | |
471 | |
|
|
472 | See L<OBJECT SERIALISATION> for details. |
|
|
473 | |
488 | If C<$enable> is true (or missing), then the C<encode> method will not |
474 | If C<$enable> is true (or missing), then the C<encode> method will not |
489 | barf when it encounters a blessed reference. Instead, the value of the |
475 | barf when it encounters a blessed reference that it cannot convert |
490 | B<convert_blessed> option will decide whether C<null> (C<convert_blessed> |
476 | otherwise. Instead, a JSON C<null> value is encoded instead of the object. |
491 | disabled or no C<TO_JSON> method found) or a representation of the |
|
|
492 | object (C<convert_blessed> enabled and C<TO_JSON> method found) is being |
|
|
493 | encoded. Has no effect on C<decode>. |
|
|
494 | |
477 | |
495 | If C<$enable> is false (the default), then C<encode> will throw an |
478 | If C<$enable> is false (the default), then C<encode> will throw an |
496 | exception when it encounters a blessed object. |
479 | exception when it encounters a blessed object that it cannot convert |
|
|
480 | otherwise. |
|
|
481 | |
|
|
482 | This setting has no effect on C<decode>. |
497 | |
483 | |
498 | =item $json = $json->convert_blessed ([$enable]) |
484 | =item $json = $json->convert_blessed ([$enable]) |
499 | |
485 | |
500 | =item $enabled = $json->get_convert_blessed |
486 | =item $enabled = $json->get_convert_blessed |
|
|
487 | |
|
|
488 | See "OBJECT SERIALISATION" for details. |
501 | |
489 | |
502 | If C<$enable> is true (or missing), then C<encode>, upon encountering a |
490 | If C<$enable> is true (or missing), then C<encode>, upon encountering a |
503 | blessed object, will check for the availability of the C<TO_JSON> method |
491 | blessed object, will check for the availability of the C<TO_JSON> method |
504 | on the object's class. If found, it will be called in scalar context |
492 | on the object's class. If found, it will be called in scalar context and |
505 | and the resulting scalar will be encoded instead of the object. If no |
493 | the resulting scalar will be encoded instead of the object. |
506 | C<TO_JSON> method is found, the value of C<allow_blessed> will decide what |
|
|
507 | to do. |
|
|
508 | |
494 | |
509 | The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON> |
495 | The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON> |
510 | returns other blessed objects, those will be handled in the same |
496 | returns other blessed objects, those will be handled in the same |
511 | way. C<TO_JSON> must take care of not causing an endless recursion cycle |
497 | way. C<TO_JSON> must take care of not causing an endless recursion cycle |
512 | (== crash) in this case. The name of C<TO_JSON> was chosen because other |
498 | (== crash) in this case. The name of C<TO_JSON> was chosen because other |
513 | methods called by the Perl core (== not by the user of the object) are |
499 | methods called by the Perl core (== not by the user of the object) are |
514 | usually in upper case letters and to avoid collisions with any C<to_json> |
500 | usually in upper case letters and to avoid collisions with any C<to_json> |
515 | function or method. |
501 | function or method. |
516 | |
502 | |
517 | This setting does not yet influence C<decode> in any way, but in the |
503 | If C<$enable> is false (the default), then C<encode> will not consider |
518 | future, global hooks might get installed that influence C<decode> and are |
504 | this type of conversion. |
519 | enabled by this setting. |
|
|
520 | |
505 | |
521 | If C<$enable> is false, then the C<allow_blessed> setting will decide what |
506 | This setting has no effect on C<decode>. |
522 | to do when a blessed object is found. |
507 | |
|
|
508 | =item $json = $json->allow_tags ([$enable]) |
|
|
509 | |
|
|
510 | =item $enabled = $json->allow_tags |
|
|
511 | |
|
|
512 | See "OBJECT SERIALISATION" for details. |
|
|
513 | |
|
|
514 | If C<$enable> is true (or missing), then C<encode>, upon encountering a |
|
|
515 | blessed object, will check for the availability of the C<FREEZE> method on |
|
|
516 | the object's class. If found, it will be used to serialise the object into |
|
|
517 | a nonstandard tagged JSON value (that JSON decoders cannot decode). |
|
|
518 | |
|
|
519 | It also causes C<decode> to parse such tagged JSON values and deserialise |
|
|
520 | them via a call to the C<THAW> method. |
|
|
521 | |
|
|
522 | If C<$enable> is false (the default), then C<encode> will not consider |
|
|
523 | this type of conversion, and tagged JSON values will cause a parse error |
|
|
524 | in C<decode>, as if tags were not part of the grammar. |
523 | |
525 | |
524 | =item $json = $json->filter_json_object ([$coderef->($hashref)]) |
526 | =item $json = $json->filter_json_object ([$coderef->($hashref)]) |
525 | |
527 | |
526 | When C<$coderef> is specified, it will be called from C<decode> each |
528 | When C<$coderef> is specified, it will be called from C<decode> each |
527 | time it decodes a JSON object. The only argument is a reference to the |
529 | time it decodes a JSON object. The only argument is a reference to the |
… | |
… | |
666 | |
668 | |
667 | See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
669 | See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
668 | |
670 | |
669 | =item $json_text = $json->encode ($perl_scalar) |
671 | =item $json_text = $json->encode ($perl_scalar) |
670 | |
672 | |
671 | Converts the given Perl data structure (a simple scalar or a reference |
673 | 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 |
674 | 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 | |
675 | |
678 | =item $perl_scalar = $json->decode ($json_text) |
676 | =item $perl_scalar = $json->decode ($json_text) |
679 | |
677 | |
680 | The opposite of C<encode>: expects a JSON text and tries to parse it, |
678 | 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. |
679 | 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 | |
680 | |
687 | =item ($perl_scalar, $characters) = $json->decode_prefix ($json_text) |
681 | =item ($perl_scalar, $characters) = $json->decode_prefix ($json_text) |
688 | |
682 | |
689 | This works like the C<decode> method, but instead of raising an exception |
683 | 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 |
684 | when there is trailing garbage after the first JSON object, it will |
691 | silently stop parsing there and return the number of characters consumed |
685 | silently stop parsing there and return the number of characters consumed |
692 | so far. |
686 | so far. |
693 | |
687 | |
694 | This is useful if your JSON texts are not delimited by an outer protocol |
688 | 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. |
689 | and you need to know where the JSON text ends. |
697 | |
690 | |
698 | JSON::XS->new->decode_prefix ("[1] the tail") |
691 | JSON::XS->new->decode_prefix ("[1] the tail") |
699 | => ([], 3) |
692 | => ([], 3) |
700 | |
693 | |
701 | =back |
694 | =back |
… | |
… | |
713 | calls). |
706 | calls). |
714 | |
707 | |
715 | JSON::XS will only attempt to parse the JSON text once it is sure it |
708 | JSON::XS will only attempt to parse the JSON text once it is sure it |
716 | has enough text to get a decisive result, using a very simple but |
709 | has enough text to get a decisive result, using a very simple but |
717 | truly incremental parser. This means that it sometimes won't stop as |
710 | truly incremental parser. This means that it sometimes won't stop as |
718 | early as the full parser, for example, it doesn't detect parenthese |
711 | early as the full parser, for example, it doesn't detect mismatched |
719 | mismatches. The only thing it guarantees is that it starts decoding as |
712 | parentheses. The only thing it guarantees is that it starts decoding as |
720 | soon as a syntactically valid JSON text has been seen. This means you need |
713 | soon as a syntactically valid JSON text has been seen. This means you need |
721 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
714 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
722 | parsing in the presence if syntax errors. |
715 | parsing in the presence if syntax errors. |
723 | |
716 | |
724 | The following methods implement this incremental parser. |
717 | The following methods implement this incremental parser. |
… | |
… | |
740 | |
733 | |
741 | If the method is called in scalar context, then it will try to extract |
734 | 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 |
735 | 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, |
736 | 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 |
737 | 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 |
738 | C<incr_skip> to skip the erroneous part). This is the most common way of |
746 | using the method. |
739 | using the method. |
747 | |
740 | |
748 | And finally, in list context, it will try to extract as many objects |
741 | 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 |
742 | 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 |
743 | otherwise. For this to work, there must be no separators between the JSON |
751 | objects or arrays, instead they must be concatenated back-to-back. If |
744 | objects or arrays, instead they must be concatenated back-to-back. If |
752 | an error occurs, an exception will be raised as in the scalar context |
745 | an error occurs, an exception will be raised as in the scalar context |
753 | case. Note that in this case, any previously-parsed JSON texts will be |
746 | case. Note that in this case, any previously-parsed JSON texts will be |
754 | lost. |
747 | lost. |
755 | |
748 | |
|
|
749 | Example: Parse some JSON arrays/objects in a given string and return |
|
|
750 | them. |
|
|
751 | |
|
|
752 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
|
|
753 | |
756 | =item $lvalue_string = $json->incr_text |
754 | =item $lvalue_string = $json->incr_text |
757 | |
755 | |
758 | This method returns the currently stored JSON fragment as an lvalue, that |
756 | This method returns the currently stored JSON fragment as an lvalue, that |
759 | is, you can manipulate it. This I<only> works when a preceding call to |
757 | is, you can manipulate it. This I<only> works when a preceding call to |
760 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
758 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
… | |
… | |
774 | C<incr_parse> died, in which case the input buffer and incremental parser |
772 | C<incr_parse> died, in which case the input buffer and incremental parser |
775 | state is left unchanged, to skip the text parsed so far and to reset the |
773 | state is left unchanged, to skip the text parsed so far and to reset the |
776 | parse state. |
774 | parse state. |
777 | |
775 | |
778 | The difference to C<incr_reset> is that only text until the parse error |
776 | The difference to C<incr_reset> is that only text until the parse error |
779 | occured is removed. |
777 | occurred is removed. |
780 | |
778 | |
781 | =item $json->incr_reset |
779 | =item $json->incr_reset |
782 | |
780 | |
783 | This completely resets the incremental parser, that is, after this call, |
781 | This completely resets the incremental parser, that is, after this call, |
784 | it will be as if the parser had never parsed anything. |
782 | it will be as if the parser had never parsed anything. |
… | |
… | |
790 | =back |
788 | =back |
791 | |
789 | |
792 | =head2 LIMITATIONS |
790 | =head2 LIMITATIONS |
793 | |
791 | |
794 | All options that affect decoding are supported, except |
792 | All options that affect decoding are supported, except |
795 | C<allow_nonref>. The reason for this is that it cannot be made to |
793 | C<allow_nonref>. The reason for this is that it cannot be made to work |
796 | work sensibly: JSON objects and arrays are self-delimited, i.e. you can concatenate |
794 | sensibly: JSON objects and arrays are self-delimited, i.e. you can |
797 | them back to back and still decode them perfectly. This does not hold true |
795 | concatenate them back to back and still decode them perfectly. This does |
798 | for JSON numbers, however. |
796 | not hold true for JSON numbers, however. |
799 | |
797 | |
800 | For example, is the string C<1> a single JSON number, or is it simply the |
798 | For example, is the string C<1> a single JSON number, or is it simply the |
801 | start of C<12>? Or is C<12> a single JSON number, or the concatenation |
799 | start of C<12>? Or is C<12> a single JSON number, or the concatenation |
802 | of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS |
800 | of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS |
803 | takes the conservative route and disallows this case. |
801 | takes the conservative route and disallows this case. |
… | |
… | |
982 | If the number consists of digits only, JSON::XS will try to represent |
980 | If the number consists of digits only, JSON::XS will try to represent |
983 | it as an integer value. If that fails, it will try to represent it as |
981 | it as an integer value. If that fails, it will try to represent it as |
984 | a numeric (floating point) value if that is possible without loss of |
982 | a numeric (floating point) value if that is possible without loss of |
985 | precision. Otherwise it will preserve the number as a string value (in |
983 | precision. Otherwise it will preserve the number as a string value (in |
986 | which case you lose roundtripping ability, as the JSON number will be |
984 | which case you lose roundtripping ability, as the JSON number will be |
987 | re-encoded toa JSON string). |
985 | re-encoded to a JSON string). |
988 | |
986 | |
989 | Numbers containing a fractional or exponential part will always be |
987 | Numbers containing a fractional or exponential part will always be |
990 | represented as numeric (floating point) values, possibly at a loss of |
988 | represented as numeric (floating point) values, possibly at a loss of |
991 | precision (in which case you might lose perfect roundtripping ability, but |
989 | precision (in which case you might lose perfect roundtripping ability, but |
992 | the JSON number will still be re-encoded as a JSON number). |
990 | the JSON number will still be re-encoded as a JSON number). |
993 | |
991 | |
|
|
992 | Note that precision is not accuracy - binary floating point values cannot |
|
|
993 | represent most decimal fractions exactly, and when converting from and to |
|
|
994 | floating point, JSON::XS only guarantees precision up to but not including |
|
|
995 | the least significant bit. |
|
|
996 | |
994 | =item true, false |
997 | =item true, false |
995 | |
998 | |
996 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
999 | These JSON atoms become C<Types::Serialiser::true> and |
997 | respectively. They are overloaded to act almost exactly like the numbers |
1000 | C<Types::Serialiser::false>, respectively. They are overloaded to act |
998 | C<1> and C<0>. You can check whether a scalar is a JSON boolean by using |
1001 | almost exactly like the numbers C<1> and C<0>. You can check whether |
999 | the C<JSON::XS::is_bool> function. |
1002 | a scalar is a JSON boolean by using the C<Types::Serialiser::is_bool> |
|
|
1003 | function (after C<use Types::Serialier>, of course). |
1000 | |
1004 | |
1001 | =item null |
1005 | =item null |
1002 | |
1006 | |
1003 | A JSON null atom becomes C<undef> in Perl. |
1007 | A JSON null atom becomes C<undef> in Perl. |
|
|
1008 | |
|
|
1009 | =item shell-style comments (C<< # I<text> >>) |
|
|
1010 | |
|
|
1011 | As a nonstandard extension to the JSON syntax that is enabled by the |
|
|
1012 | C<relaxed> setting, shell-style comments are allowed. They can start |
|
|
1013 | anywhere outside strings and go till the end of the line. |
|
|
1014 | |
|
|
1015 | =item tagged values (C<< (I<tag>)I<value> >>). |
|
|
1016 | |
|
|
1017 | Another nonstandard extension to the JSON syntax, enabled with the |
|
|
1018 | C<allow_tags> setting, are tagged values. In this implementation, the |
|
|
1019 | I<tag> must be a perl package/class name encoded as a JSON string, and the |
|
|
1020 | I<value> must be a JSON array encoding optional constructor arguments. |
|
|
1021 | |
|
|
1022 | See "OBJECT SERIALISATION", below, for details. |
1004 | |
1023 | |
1005 | =back |
1024 | =back |
1006 | |
1025 | |
1007 | |
1026 | |
1008 | =head2 PERL -> JSON |
1027 | =head2 PERL -> JSON |
… | |
… | |
1013 | |
1032 | |
1014 | =over 4 |
1033 | =over 4 |
1015 | |
1034 | |
1016 | =item hash references |
1035 | =item hash references |
1017 | |
1036 | |
1018 | Perl hash references become JSON objects. As there is no inherent ordering |
1037 | Perl hash references become JSON objects. As there is no inherent |
1019 | in hash keys (or JSON objects), they will usually be encoded in a |
1038 | ordering in hash keys (or JSON objects), they will usually be encoded |
1020 | pseudo-random order that can change between runs of the same program but |
1039 | in a pseudo-random order. JSON::XS can optionally sort the hash keys |
1021 | stays generally the same within a single run of a program. JSON::XS can |
1040 | (determined by the I<canonical> flag), so the same datastructure will |
1022 | optionally sort the hash keys (determined by the I<canonical> flag), so |
1041 | serialise to the same JSON text (given same settings and version of |
1023 | the same datastructure will serialise to the same JSON text (given same |
1042 | JSON::XS), but this incurs a runtime overhead and is only rarely useful, |
1024 | settings and version of JSON::XS), but this incurs a runtime overhead |
1043 | e.g. when you want to compare some JSON text against another for equality. |
1025 | and is only rarely useful, e.g. when you want to compare some JSON text |
|
|
1026 | against another for equality. |
|
|
1027 | |
1044 | |
1028 | =item array references |
1045 | =item array references |
1029 | |
1046 | |
1030 | Perl array references become JSON arrays. |
1047 | Perl array references become JSON arrays. |
1031 | |
1048 | |
1032 | =item other references |
1049 | =item other references |
1033 | |
1050 | |
1034 | Other unblessed references are generally not allowed and will cause an |
1051 | Other unblessed references are generally not allowed and will cause an |
1035 | exception to be thrown, except for references to the integers C<0> and |
1052 | exception to be thrown, except for references to the integers C<0> and |
1036 | C<1>, which get turned into C<false> and C<true> atoms in JSON. You can |
1053 | C<1>, which get turned into C<false> and C<true> atoms in JSON. |
1037 | also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability. |
|
|
1038 | |
1054 | |
|
|
1055 | Since C<JSON::XS> uses the boolean model from L<Types::Serialiser>, you |
|
|
1056 | can also C<use Types::Serialiser> and then use C<Types::Serialiser::false> |
|
|
1057 | and C<Types::Serialiser::true> to improve readability. |
|
|
1058 | |
|
|
1059 | use Types::Serialiser; |
1039 | encode_json [\0, JSON::XS::true] # yields [false,true] |
1060 | encode_json [\0, Types::Serialiser::true] # yields [false,true] |
1040 | |
1061 | |
1041 | =item JSON::XS::true, JSON::XS::false |
1062 | =item Types::Serialiser::true, Types::Serialiser::false |
1042 | |
1063 | |
1043 | These special values become JSON true and JSON false values, |
1064 | These special values from the L<Types::Serialiser> module become JSON true |
1044 | respectively. You can also use C<\1> and C<\0> directly if you want. |
1065 | and JSON false values, respectively. You can also use C<\1> and C<\0> |
|
|
1066 | directly if you want. |
1045 | |
1067 | |
1046 | =item blessed objects |
1068 | =item blessed objects |
1047 | |
1069 | |
1048 | Blessed objects are not directly representable in JSON. See the |
1070 | Blessed objects are not directly representable in JSON, but C<JSON::XS> |
1049 | C<allow_blessed> and C<convert_blessed> methods on various options on |
1071 | allows various ways of handling objects. See "OBJECT SERIALISATION", |
1050 | how to deal with this: basically, you can choose between throwing an |
1072 | below, for details. |
1051 | exception, encoding the reference as if it weren't blessed, or provide |
|
|
1052 | your own serialiser method. |
|
|
1053 | |
1073 | |
1054 | =item simple scalars |
1074 | =item simple scalars |
1055 | |
1075 | |
1056 | Simple Perl scalars (any scalar that is not a reference) are the most |
1076 | Simple Perl scalars (any scalar that is not a reference) are the most |
1057 | difficult objects to encode: JSON::XS will encode undefined scalars as |
1077 | difficult objects to encode: JSON::XS will encode undefined scalars as |
… | |
… | |
1085 | |
1105 | |
1086 | You can not currently force the type in other, less obscure, ways. Tell me |
1106 | You can not currently force the type in other, less obscure, ways. Tell me |
1087 | if you need this capability (but don't forget to explain why it's needed |
1107 | if you need this capability (but don't forget to explain why it's needed |
1088 | :). |
1108 | :). |
1089 | |
1109 | |
|
|
1110 | Note that numerical precision has the same meaning as under Perl (so |
|
|
1111 | binary to decimal conversion follows the same rules as in Perl, which |
|
|
1112 | can differ to other languages). Also, your perl interpreter might expose |
|
|
1113 | extensions to the floating point numbers of your platform, such as |
|
|
1114 | infinities or NaN's - these cannot be represented in JSON, and it is an |
|
|
1115 | error to pass those in. |
|
|
1116 | |
1090 | =back |
1117 | =back |
|
|
1118 | |
|
|
1119 | =head2 OBJECT SERIALISATION |
|
|
1120 | |
|
|
1121 | As JSON cannot directly represent Perl objects, you have to choose between |
|
|
1122 | a pure JSON representation (without the ability to deserialise the object |
|
|
1123 | automatically again), and a nonstandard extension to the JSON syntax, |
|
|
1124 | tagged values. |
|
|
1125 | |
|
|
1126 | =head3 SERIALISATION |
|
|
1127 | |
|
|
1128 | What happens when C<JSON::XS> encounters a Perl object depends on the |
|
|
1129 | C<allow_blessed>, C<convert_blessed> and C<allow_tags> settings, which are |
|
|
1130 | used in this order: |
|
|
1131 | |
|
|
1132 | =over 4 |
|
|
1133 | |
|
|
1134 | =item 1. C<allow_tags> is enabled and object has a C<FREEZE> method. |
|
|
1135 | |
|
|
1136 | In this case, C<JSON::XS> uses the L<Types::Serialiser> object |
|
|
1137 | serialisation protocol to create a tagged JSON value, using a nonstandard |
|
|
1138 | extension to the JSON syntax. |
|
|
1139 | |
|
|
1140 | This works by invoking the C<FREEZE> method on the object, with the first |
|
|
1141 | argument being the object to serialise, and the second argument being the |
|
|
1142 | constant string C<JSON> to distinguish it from other serialisers. |
|
|
1143 | |
|
|
1144 | The C<FREEZE> method can return any number of values (i.e. zero or |
|
|
1145 | more). These values and the paclkage/classname of the object will then be |
|
|
1146 | encoded as a tagged JSON value in the following format: |
|
|
1147 | |
|
|
1148 | ("classname")[FREEZE return values...] |
|
|
1149 | |
|
|
1150 | For example, the hypothetical C<My::Object> C<FREEZE> method might use the |
|
|
1151 | objects C<type> and C<id> members to encode the object: |
|
|
1152 | |
|
|
1153 | sub My::Object::FREEZE { |
|
|
1154 | my ($self, $serialiser) = @_; |
|
|
1155 | |
|
|
1156 | ($self->{type}, $self->{id}) |
|
|
1157 | } |
|
|
1158 | |
|
|
1159 | =item 2. C<convert_blessed> is enabled and object has a C<TO_JSON> method. |
|
|
1160 | |
|
|
1161 | In this case, the C<TO_JSON> method of the object is invoked in scalar |
|
|
1162 | context. It must return a single scalar that can be directly encoded into |
|
|
1163 | JSON. This scalar replaces the object in the JSON text. |
|
|
1164 | |
|
|
1165 | For example, the following C<TO_JSON> method will convert all L<URI> |
|
|
1166 | objects to JSON strings when serialised. The fatc that these values |
|
|
1167 | originally were L<URI> objects is lost. |
|
|
1168 | |
|
|
1169 | sub URI::TO_JSON { |
|
|
1170 | my ($uri) = @_; |
|
|
1171 | $uri->as_string |
|
|
1172 | } |
|
|
1173 | |
|
|
1174 | =item 3. C<allow_blessed> is enabled. |
|
|
1175 | |
|
|
1176 | The object will be serialised as a JSON null value. |
|
|
1177 | |
|
|
1178 | =item 4. none of the above |
|
|
1179 | |
|
|
1180 | If none of the settings are enabled or the respective methods are missing, |
|
|
1181 | C<JSON::XS> throws an exception. |
|
|
1182 | |
|
|
1183 | =back |
|
|
1184 | |
|
|
1185 | =head3 DESERIALISATION |
|
|
1186 | |
|
|
1187 | For deserialisation there are only two cases to consider: either |
|
|
1188 | nonstandard tagging was used, in which case C<allow_tags> decides, |
|
|
1189 | or objects cannot be automatically be deserialised, in which |
|
|
1190 | case you can use postprocessing or the C<filter_json_object> or |
|
|
1191 | C<filter_json_single_key_object> callbacks to get some real objects our of |
|
|
1192 | your JSON. |
|
|
1193 | |
|
|
1194 | This section only considers the tagged value case: I a tagged JSON object |
|
|
1195 | is encountered during decoding and C<allow_tags> is disabled, a parse |
|
|
1196 | error will result (as if tagged values were not part of the grammar). |
|
|
1197 | |
|
|
1198 | If C<allow_tags> is enabled, C<JSON::XS> will look up the C<THAW> method |
|
|
1199 | of the package/classname used during serialisation (it will not attempt |
|
|
1200 | to load the package as a Perl module). If there is no such method, the |
|
|
1201 | decoding will fail with an error. |
|
|
1202 | |
|
|
1203 | Otherwise, the C<THAW> method is invoked with the classname as first |
|
|
1204 | argument, the constant string C<JSON> as second argument, and all the |
|
|
1205 | values from the JSON array (the values originally returned by the |
|
|
1206 | C<FREEZE> method) as remaining arguments. |
|
|
1207 | |
|
|
1208 | The method must then return the object. While technically you can return |
|
|
1209 | any Perl scalar, you might have to enable the C<enable_nonref> setting to |
|
|
1210 | make that work in all cases, so better return an actual blessed reference. |
|
|
1211 | |
|
|
1212 | As an example, let's implement a C<THAW> function that regenerates the |
|
|
1213 | C<My::Object> from the C<FREEZE> example earlier: |
|
|
1214 | |
|
|
1215 | sub My::Object::THAW { |
|
|
1216 | my ($class, $serialiser, $type, $id) = @_; |
|
|
1217 | |
|
|
1218 | $class->new (type => $type, id => $id) |
|
|
1219 | } |
1091 | |
1220 | |
1092 | |
1221 | |
1093 | =head1 ENCODING/CODESET FLAG NOTES |
1222 | =head1 ENCODING/CODESET FLAG NOTES |
1094 | |
1223 | |
1095 | The interested reader might have seen a number of flags that signify |
1224 | The interested reader might have seen a number of flags that signify |
… | |
… | |
1120 | =item C<utf8> flag disabled |
1249 | =item C<utf8> flag disabled |
1121 | |
1250 | |
1122 | When C<utf8> is disabled (the default), then C<encode>/C<decode> generate |
1251 | When C<utf8> is disabled (the default), then C<encode>/C<decode> generate |
1123 | and expect Unicode strings, that is, characters with high ordinal Unicode |
1252 | and expect Unicode strings, that is, characters with high ordinal Unicode |
1124 | values (> 255) will be encoded as such characters, and likewise such |
1253 | values (> 255) will be encoded as such characters, and likewise such |
1125 | characters are decoded as-is, no canges to them will be done, except |
1254 | characters are decoded as-is, no changes to them will be done, except |
1126 | "(re-)interpreting" them as Unicode codepoints or Unicode characters, |
1255 | "(re-)interpreting" them as Unicode codepoints or Unicode characters, |
1127 | respectively (to Perl, these are the same thing in strings unless you do |
1256 | respectively (to Perl, these are the same thing in strings unless you do |
1128 | funny/weird/dumb stuff). |
1257 | funny/weird/dumb stuff). |
1129 | |
1258 | |
1130 | This is useful when you want to do the encoding yourself (e.g. when you |
1259 | This is useful when you want to do the encoding yourself (e.g. when you |
… | |
… | |
1238 | well - using C<eval> naively simply I<will> cause problems. |
1367 | well - using C<eval> naively simply I<will> cause problems. |
1239 | |
1368 | |
1240 | Another problem is that some javascript implementations reserve |
1369 | Another problem is that some javascript implementations reserve |
1241 | some property names for their own purposes (which probably makes |
1370 | some property names for their own purposes (which probably makes |
1242 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
1371 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
1243 | C<__proto__> property name for it's own purposes. |
1372 | C<__proto__> property name for its own purposes. |
1244 | |
1373 | |
1245 | If that is a problem, you could parse try to filter the resulting JSON |
1374 | If that is a problem, you could parse try to filter the resulting JSON |
1246 | output for these property strings, e.g.: |
1375 | output for these property strings, e.g.: |
1247 | |
1376 | |
1248 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
1377 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
1249 | |
1378 | |
1250 | This works because C<__proto__> is not valid outside of strings, so every |
1379 | This works because C<__proto__> is not valid outside of strings, so every |
1251 | occurence of C<"__proto__"\s*:> must be a string used as property name. |
1380 | occurrence of C<"__proto__"\s*:> must be a string used as property name. |
1252 | |
1381 | |
1253 | If you know of other incompatibilities, please let me know. |
1382 | If you know of other incompatibilities, please let me know. |
1254 | |
1383 | |
1255 | |
1384 | |
1256 | =head2 JSON and YAML |
1385 | =head2 JSON and YAML |
… | |
… | |
1268 | my $yaml = $to_yaml->encode ($ref) . "\n"; |
1397 | my $yaml = $to_yaml->encode ($ref) . "\n"; |
1269 | |
1398 | |
1270 | This will I<usually> generate JSON texts that also parse as valid |
1399 | This will I<usually> generate JSON texts that also parse as valid |
1271 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1400 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1272 | lengths that JSON doesn't have and also has different and incompatible |
1401 | lengths that JSON doesn't have and also has different and incompatible |
1273 | unicode handling, so you should make sure that your hash keys are |
1402 | unicode character escape syntax, so you should make sure that your hash |
1274 | noticeably shorter than the 1024 "stream characters" YAML allows and that |
1403 | keys are noticeably shorter than the 1024 "stream characters" YAML allows |
1275 | you do not have characters with codepoint values outside the Unicode BMP |
1404 | and that you do not have characters with codepoint values outside the |
1276 | (basic multilingual page). YAML also does not allow C<\/> sequences in |
1405 | Unicode BMP (basic multilingual page). YAML also does not allow C<\/> |
1277 | strings (which JSON::XS does not I<currently> generate, but other JSON |
1406 | sequences in strings (which JSON::XS does not I<currently> generate, but |
1278 | generators might). |
1407 | other JSON generators might). |
1279 | |
1408 | |
1280 | There might be other incompatibilities that I am not aware of (or the YAML |
1409 | There might be other incompatibilities that I am not aware of (or the YAML |
1281 | specification has been changed yet again - it does so quite often). In |
1410 | specification has been changed yet again - it does so quite often). In |
1282 | general you should not try to generate YAML with a JSON generator or vice |
1411 | general you should not try to generate YAML with a JSON generator or vice |
1283 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
1412 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
… | |
… | |
1302 | that difficult or long) and finally make YAML compatible to it, and |
1431 | that difficult or long) and finally make YAML compatible to it, and |
1303 | educating users about the changes, instead of spreading lies about the |
1432 | educating users about the changes, instead of spreading lies about the |
1304 | real compatibility for many I<years> and trying to silence people who |
1433 | real compatibility for many I<years> and trying to silence people who |
1305 | point out that it isn't true. |
1434 | point out that it isn't true. |
1306 | |
1435 | |
|
|
1436 | Addendum/2009: the YAML 1.2 spec is still incompatible with JSON, even |
|
|
1437 | though the incompatibilities have been documented (and are known to Brian) |
|
|
1438 | for many years and the spec makes explicit claims that YAML is a superset |
|
|
1439 | of JSON. It would be so easy to fix, but apparently, bullying people and |
|
|
1440 | corrupting userdata is so much easier. |
|
|
1441 | |
1307 | =back |
1442 | =back |
1308 | |
1443 | |
1309 | |
1444 | |
1310 | =head2 SPEED |
1445 | =head2 SPEED |
1311 | |
1446 | |
… | |
… | |
1318 | a very short single-line JSON string (also available at |
1453 | a very short single-line JSON string (also available at |
1319 | L<http://dist.schmorp.de/misc/json/short.json>). |
1454 | L<http://dist.schmorp.de/misc/json/short.json>). |
1320 | |
1455 | |
1321 | {"method": "handleMessage", "params": ["user1", |
1456 | {"method": "handleMessage", "params": ["user1", |
1322 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
1457 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
1323 | true, false]} |
1458 | 1, 0]} |
1324 | |
1459 | |
1325 | It shows the number of encodes/decodes per second (JSON::XS uses |
1460 | It shows the number of encodes/decodes per second (JSON::XS uses |
1326 | the functional interface, while JSON::XS/2 uses the OO interface |
1461 | the functional interface, while JSON::XS/2 uses the OO interface |
1327 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
1462 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
1328 | shrink). Higher is better: |
1463 | shrink. JSON::DWIW/DS uses the deserialise function, while JSON::DWIW::FJ |
|
|
1464 | uses the from_json method). Higher is better: |
1329 | |
1465 | |
1330 | module | encode | decode | |
1466 | module | encode | decode | |
1331 | -----------|------------|------------| |
1467 | --------------|------------|------------| |
1332 | JSON 1.x | 4990.842 | 4088.813 | |
1468 | JSON::DWIW/DS | 86302.551 | 102300.098 | |
1333 | JSON::DWIW | 51653.990 | 71575.154 | |
1469 | JSON::DWIW/FJ | 86302.551 | 75983.768 | |
1334 | JSON::PC | 65948.176 | 74631.744 | |
1470 | JSON::PP | 15827.562 | 6638.658 | |
1335 | JSON::PP | 8931.652 | 3817.168 | |
1471 | JSON::Syck | 63358.066 | 47662.545 | |
1336 | JSON::Syck | 24877.248 | 27776.848 | |
1472 | JSON::XS | 511500.488 | 511500.488 | |
1337 | JSON::XS | 388361.481 | 227951.304 | |
1473 | JSON::XS/2 | 291271.111 | 388361.481 | |
1338 | JSON::XS/2 | 227951.304 | 218453.333 | |
1474 | JSON::XS/3 | 361577.931 | 361577.931 | |
1339 | JSON::XS/3 | 338250.323 | 218453.333 | |
1475 | Storable | 66788.280 | 265462.278 | |
1340 | Storable | 16500.016 | 135300.129 | |
|
|
1341 | -----------+------------+------------+ |
1476 | --------------+------------+------------+ |
1342 | |
1477 | |
1343 | That is, JSON::XS is about five times faster than JSON::DWIW on encoding, |
1478 | That is, JSON::XS is almost six times faster than JSON::DWIW on encoding, |
1344 | about three times faster on decoding, and over forty times faster |
1479 | about five times faster on decoding, and over thirty to seventy times |
1345 | than JSON, even with pretty-printing and key sorting. It also compares |
1480 | faster than JSON's pure perl implementation. It also compares favourably |
1346 | favourably to Storable for small amounts of data. |
1481 | to Storable for small amounts of data. |
1347 | |
1482 | |
1348 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1483 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1349 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
1484 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
1350 | |
1485 | |
1351 | module | encode | decode | |
1486 | module | encode | decode | |
1352 | -----------|------------|------------| |
1487 | --------------|------------|------------| |
1353 | JSON 1.x | 55.260 | 34.971 | |
1488 | JSON::DWIW/DS | 1647.927 | 2673.916 | |
1354 | JSON::DWIW | 825.228 | 1082.513 | |
1489 | JSON::DWIW/FJ | 1630.249 | 2596.128 | |
1355 | JSON::PC | 3571.444 | 2394.829 | |
|
|
1356 | JSON::PP | 210.987 | 32.574 | |
1490 | JSON::PP | 400.640 | 62.311 | |
1357 | JSON::Syck | 552.551 | 787.544 | |
1491 | JSON::Syck | 1481.040 | 1524.869 | |
1358 | JSON::XS | 5780.463 | 4854.519 | |
1492 | JSON::XS | 20661.596 | 9541.183 | |
1359 | JSON::XS/2 | 3869.998 | 4798.975 | |
1493 | JSON::XS/2 | 10683.403 | 9416.938 | |
1360 | JSON::XS/3 | 5862.880 | 4798.975 | |
1494 | JSON::XS/3 | 20661.596 | 9400.054 | |
1361 | Storable | 4445.002 | 5235.027 | |
1495 | Storable | 19765.806 | 10000.725 | |
1362 | -----------+------------+------------+ |
1496 | --------------+------------+------------+ |
1363 | |
1497 | |
1364 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
1498 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
1365 | decodes faster). |
1499 | decodes a bit faster). |
1366 | |
1500 | |
1367 | On large strings containing lots of high Unicode characters, some modules |
1501 | On large strings containing lots of high Unicode characters, some modules |
1368 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
1502 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
1369 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
1503 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
1370 | to decode or encode properly, so it was impossible to prepare a fair |
1504 | to decode or encode properly, so it was impossible to prepare a fair |
… | |
… | |
1406 | information you might want to make sure that exceptions thrown by JSON::XS |
1540 | information you might want to make sure that exceptions thrown by JSON::XS |
1407 | will not end up in front of untrusted eyes. |
1541 | will not end up in front of untrusted eyes. |
1408 | |
1542 | |
1409 | If you are using JSON::XS to return packets to consumption |
1543 | If you are using JSON::XS to return packets to consumption |
1410 | by JavaScript scripts in a browser you should have a look at |
1544 | by JavaScript scripts in a browser you should have a look at |
1411 | L<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether |
1545 | L<http://blog.archive.jpsykes.com/47/practical-csrf-and-json-security/> to |
1412 | you are vulnerable to some common attack vectors (which really are browser |
1546 | see whether you are vulnerable to some common attack vectors (which really |
1413 | design bugs, but it is still you who will have to deal with it, as major |
1547 | are browser design bugs, but it is still you who will have to deal with |
1414 | browser developers care only for features, not about getting security |
1548 | it, as major browser developers care only for features, not about getting |
1415 | right). |
1549 | security right). |
|
|
1550 | |
|
|
1551 | |
|
|
1552 | =head1 INTEROPERABILITY WITH OTHER MODULES |
|
|
1553 | |
|
|
1554 | C<JSON::XS> uses the L<Types::Serialiser> module to provide boolean |
|
|
1555 | constants. That means that the JSON true and false values will be |
|
|
1556 | comaptible to true and false values of iother modules that do the same, |
|
|
1557 | such as L<JSON::PP> and L<CBOR::XS>. |
1416 | |
1558 | |
1417 | |
1559 | |
1418 | =head1 THREADS |
1560 | =head1 THREADS |
1419 | |
1561 | |
1420 | This module is I<not> guaranteed to be thread safe and there are no |
1562 | This module is I<not> guaranteed to be thread safe and there are no |
… | |
… | |
1423 | process simulations - use fork, it's I<much> faster, cheaper, better). |
1565 | process simulations - use fork, it's I<much> faster, cheaper, better). |
1424 | |
1566 | |
1425 | (It might actually work, but you have been warned). |
1567 | (It might actually work, but you have been warned). |
1426 | |
1568 | |
1427 | |
1569 | |
|
|
1570 | =head1 THE PERILS OF SETLOCALE |
|
|
1571 | |
|
|
1572 | Sometimes people avoid the Perl locale support and directly call the |
|
|
1573 | system's setlocale function with C<LC_ALL>. |
|
|
1574 | |
|
|
1575 | This breaks both perl and modules such as JSON::XS, as stringification of |
|
|
1576 | numbers no longer works correctly (e.g. C<$x = 0.1; print "$x"+1> might |
|
|
1577 | print C<1>, and JSON::XS might output illegal JSON as JSON::XS relies on |
|
|
1578 | perl to stringify numbers). |
|
|
1579 | |
|
|
1580 | The solution is simple: don't call C<setlocale>, or use it for only those |
|
|
1581 | categories you need, such as C<LC_MESSAGES> or C<LC_CTYPE>. |
|
|
1582 | |
|
|
1583 | If you need C<LC_NUMERIC>, you should enable it only around the code that |
|
|
1584 | actually needs it (avoiding stringification of numbers), and restore it |
|
|
1585 | afterwards. |
|
|
1586 | |
|
|
1587 | |
1428 | =head1 BUGS |
1588 | =head1 BUGS |
1429 | |
1589 | |
1430 | While the goal of this module is to be correct, that unfortunately does |
1590 | While the goal of this module is to be correct, that unfortunately does |
1431 | not mean it's bug-free, only that I think its design is bug-free. If you |
1591 | not mean it's bug-free, only that I think its design is bug-free. If you |
1432 | keep reporting bugs they will be fixed swiftly, though. |
1592 | keep reporting bugs they will be fixed swiftly, though. |
… | |
… | |
1434 | Please refrain from using rt.cpan.org or any other bug reporting |
1594 | Please refrain from using rt.cpan.org or any other bug reporting |
1435 | service. I put the contact address into my modules for a reason. |
1595 | service. I put the contact address into my modules for a reason. |
1436 | |
1596 | |
1437 | =cut |
1597 | =cut |
1438 | |
1598 | |
1439 | our $true = do { bless \(my $dummy = 1), "JSON::XS::Boolean" }; |
1599 | BEGIN { |
1440 | our $false = do { bless \(my $dummy = 0), "JSON::XS::Boolean" }; |
1600 | *true = \$Types::Serialiser::true; |
|
|
1601 | *true = \&Types::Serialiser::true; |
|
|
1602 | *false = \$Types::Serialiser::false; |
|
|
1603 | *false = \&Types::Serialiser::false; |
|
|
1604 | *is_bool = \&Types::Serialiser::is_bool; |
1441 | |
1605 | |
1442 | sub true() { $true } |
1606 | *JSON::XS::Boolean:: = *Types::Serialiser::Boolean::; |
1443 | sub false() { $false } |
|
|
1444 | |
|
|
1445 | sub is_bool($) { |
|
|
1446 | UNIVERSAL::isa $_[0], "JSON::XS::Boolean" |
|
|
1447 | # or UNIVERSAL::isa $_[0], "JSON::Literal" |
|
|
1448 | } |
1607 | } |
1449 | |
1608 | |
1450 | XSLoader::load "JSON::XS", $VERSION; |
1609 | XSLoader::load "JSON::XS", $VERSION; |
1451 | |
|
|
1452 | package JSON::XS::Boolean; |
|
|
1453 | |
|
|
1454 | use overload |
|
|
1455 | "0+" => sub { ${$_[0]} }, |
|
|
1456 | "++" => sub { $_[0] = ${$_[0]} + 1 }, |
|
|
1457 | "--" => sub { $_[0] = ${$_[0]} - 1 }, |
|
|
1458 | fallback => 1; |
|
|
1459 | |
|
|
1460 | 1; |
|
|
1461 | |
1610 | |
1462 | =head1 SEE ALSO |
1611 | =head1 SEE ALSO |
1463 | |
1612 | |
1464 | The F<json_xs> command line utility for quick experiments. |
1613 | The F<json_xs> command line utility for quick experiments. |
1465 | |
1614 | |
… | |
… | |
1468 | Marc Lehmann <schmorp@schmorp.de> |
1617 | Marc Lehmann <schmorp@schmorp.de> |
1469 | http://home.schmorp.de/ |
1618 | http://home.schmorp.de/ |
1470 | |
1619 | |
1471 | =cut |
1620 | =cut |
1472 | |
1621 | |
|
|
1622 | 1 |
|
|
1623 | |