… | |
… | |
37 | primary goal is to be I<correct> and its secondary goal is to be |
37 | primary goal is to be I<correct> and its secondary goal is to be |
38 | I<fast>. To reach the latter goal it was written in C. |
38 | I<fast>. To reach the latter goal it was written in C. |
39 | |
39 | |
40 | Beginning with version 2.0 of the JSON module, when both JSON and |
40 | Beginning with version 2.0 of the JSON module, when both JSON and |
41 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can be |
41 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can be |
42 | overriden) with no overhead due to emulation (by inheritign constructor |
42 | overridden) with no overhead due to emulation (by inheriting constructor |
43 | and methods). If JSON::XS is not available, it will fall back to the |
43 | and methods). If JSON::XS is not available, it will fall back to the |
44 | compatible JSON::PP module as backend, so using JSON instead of JSON::XS |
44 | compatible JSON::PP module as backend, so using JSON instead of JSON::XS |
45 | gives you a portable JSON API that can be fast when you need and doesn't |
45 | gives you a portable JSON API that can be fast when you need and doesn't |
46 | require a C compiler when that is a problem. |
46 | require a C compiler when that is a problem. |
47 | |
47 | |
… | |
… | |
49 | to write yet another JSON module? While it seems there are many JSON |
49 | to write yet another JSON module? While it seems there are many JSON |
50 | modules, none of them correctly handle all corner cases, and in most cases |
50 | modules, none of them correctly handle all corner cases, and in most cases |
51 | their maintainers are unresponsive, gone missing, or not listening to bug |
51 | their maintainers are unresponsive, gone missing, or not listening to bug |
52 | reports for other reasons. |
52 | reports for other reasons. |
53 | |
53 | |
54 | See COMPARISON, below, for a comparison to some other JSON modules. |
|
|
55 | |
|
|
56 | See MAPPING, below, on how JSON::XS maps perl values to JSON values and |
54 | See MAPPING, below, on how JSON::XS maps perl values to JSON values and |
57 | vice versa. |
55 | vice versa. |
58 | |
56 | |
59 | =head2 FEATURES |
57 | =head2 FEATURES |
60 | |
58 | |
… | |
… | |
65 | This module knows how to handle Unicode, documents how and when it does |
63 | This module knows how to handle Unicode, documents how and when it does |
66 | so, and even documents what "correct" means. |
64 | so, and even documents what "correct" means. |
67 | |
65 | |
68 | =item * round-trip integrity |
66 | =item * round-trip integrity |
69 | |
67 | |
70 | When you serialise a perl data structure using only datatypes supported |
68 | When you serialise a perl data structure using only data types supported |
71 | by JSON, the deserialised data structure is identical on the Perl level. |
69 | by JSON, the deserialised data structure is identical on the Perl level. |
72 | (e.g. the string "2.0" doesn't suddenly become "2" just because it looks |
70 | (e.g. the string "2.0" doesn't suddenly become "2" just because it looks |
73 | like a number). There minor I<are> exceptions to this, read the MAPPING |
71 | like a number). There minor I<are> exceptions to this, read the MAPPING |
74 | section below to learn about those. |
72 | section below to learn about those. |
75 | |
73 | |
… | |
… | |
84 | Compared to other JSON modules and other serialisers such as Storable, |
82 | Compared to other JSON modules and other serialisers such as Storable, |
85 | this module usually compares favourably in terms of speed, too. |
83 | this module usually compares favourably in terms of speed, too. |
86 | |
84 | |
87 | =item * simple to use |
85 | =item * simple to use |
88 | |
86 | |
89 | This module has both a simple functional interface as well as an objetc |
87 | This module has both a simple functional interface as well as an object |
90 | oriented interface interface. |
88 | oriented interface interface. |
91 | |
89 | |
92 | =item * reasonably versatile output formats |
90 | =item * reasonably versatile output formats |
93 | |
91 | |
94 | You can choose between the most compact guaranteed-single-line format |
92 | You can choose between the most compact guaranteed-single-line format |
95 | possible (nice for simple line-based protocols), a pure-ascii format |
93 | possible (nice for simple line-based protocols), a pure-ASCII format |
96 | (for when your transport is not 8-bit clean, still supports the whole |
94 | (for when your transport is not 8-bit clean, still supports the whole |
97 | Unicode range), or a pretty-printed format (for when you want to read that |
95 | Unicode range), or a pretty-printed format (for when you want to read that |
98 | stuff). Or you can combine those features in whatever way you like. |
96 | stuff). Or you can combine those features in whatever way you like. |
99 | |
97 | |
100 | =back |
98 | =back |
101 | |
99 | |
102 | =cut |
100 | =cut |
103 | |
101 | |
104 | package JSON::XS; |
102 | package JSON::XS; |
105 | |
103 | |
106 | use strict; |
104 | use common::sense; |
107 | |
105 | |
108 | our $VERSION = '2.2'; |
106 | our $VERSION = '2.24'; |
109 | our @ISA = qw(Exporter); |
107 | our @ISA = qw(Exporter); |
110 | |
108 | |
111 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
109 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
112 | |
110 | |
113 | sub to_json($) { |
111 | sub to_json($) { |
… | |
… | |
137 | |
135 | |
138 | This function call is functionally identical to: |
136 | This function call is functionally identical to: |
139 | |
137 | |
140 | $json_text = JSON::XS->new->utf8->encode ($perl_scalar) |
138 | $json_text = JSON::XS->new->utf8->encode ($perl_scalar) |
141 | |
139 | |
142 | except being faster. |
140 | Except being faster. |
143 | |
141 | |
144 | =item $perl_scalar = decode_json $json_text |
142 | =item $perl_scalar = decode_json $json_text |
145 | |
143 | |
146 | The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries |
144 | The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries |
147 | to parse that as an UTF-8 encoded JSON text, returning the resulting |
145 | to parse that as an UTF-8 encoded JSON text, returning the resulting |
… | |
… | |
149 | |
147 | |
150 | This function call is functionally identical to: |
148 | This function call is functionally identical to: |
151 | |
149 | |
152 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
150 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
153 | |
151 | |
154 | except being faster. |
152 | Except being faster. |
155 | |
153 | |
156 | =item $is_boolean = JSON::XS::is_bool $scalar |
154 | =item $is_boolean = JSON::XS::is_bool $scalar |
157 | |
155 | |
158 | Returns true if the passed scalar represents either JSON::XS::true or |
156 | Returns true if the passed scalar represents either JSON::XS::true or |
159 | JSON::XS::false, two constants that act like C<1> and C<0>, respectively |
157 | JSON::XS::false, two constants that act like C<1> and C<0>, respectively |
… | |
… | |
197 | |
195 | |
198 | If you didn't know about that flag, just the better, pretend it doesn't |
196 | If you didn't know about that flag, just the better, pretend it doesn't |
199 | exist. |
197 | exist. |
200 | |
198 | |
201 | =item 4. A "Unicode String" is simply a string where each character can be |
199 | =item 4. A "Unicode String" is simply a string where each character can be |
202 | validly interpreted as a Unicode codepoint. |
200 | validly interpreted as a Unicode code point. |
203 | |
201 | |
204 | If you have UTF-8 encoded data, it is no longer a Unicode string, but a |
202 | If you have UTF-8 encoded data, it is no longer a Unicode string, but a |
205 | Unicode string encoded in UTF-8, giving you a binary string. |
203 | Unicode string encoded in UTF-8, giving you a binary string. |
206 | |
204 | |
207 | =item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string. |
205 | =item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string. |
… | |
… | |
701 | =back |
699 | =back |
702 | |
700 | |
703 | |
701 | |
704 | =head1 INCREMENTAL PARSING |
702 | =head1 INCREMENTAL PARSING |
705 | |
703 | |
706 | [This section and the API it details is still EXPERIMENTAL] |
|
|
707 | |
|
|
708 | In some cases, there is the need for incremental parsing of JSON |
704 | In some cases, there is the need for incremental parsing of JSON |
709 | texts. While this module always has to keep both JSON text and resulting |
705 | texts. While this module always has to keep both JSON text and resulting |
710 | Perl data structure in memory at one time, it does allow you to parse a |
706 | Perl data structure in memory at one time, it does allow you to parse a |
711 | JSON stream incrementally. It does so by accumulating text until it has |
707 | JSON stream incrementally. It does so by accumulating text until it has |
712 | a full JSON object, which it then can decode. This process is similar to |
708 | a full JSON object, which it then can decode. This process is similar to |
713 | using C<decode_prefix> to see if a full JSON object is available, but is |
709 | using C<decode_prefix> to see if a full JSON object is available, but |
714 | much more efficient (JSON::XS will only attempt to parse the JSON text |
710 | is much more efficient (and can be implemented with a minimum of method |
|
|
711 | calls). |
|
|
712 | |
|
|
713 | JSON::XS will only attempt to parse the JSON text once it is sure it |
715 | once it is sure it has enough text to get a decisive result, using a very |
714 | has enough text to get a decisive result, using a very simple but |
716 | simple but truly incremental parser). |
715 | truly incremental parser. This means that it sometimes won't stop as |
|
|
716 | early as the full parser, for example, it doesn't detect parenthese |
|
|
717 | mismatches. The only thing it guarantees is that it starts decoding as |
|
|
718 | soon as a syntactically valid JSON text has been seen. This means you need |
|
|
719 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
|
|
720 | parsing in the presence if syntax errors. |
717 | |
721 | |
718 | The following two methods deal with this. |
722 | The following methods implement this incremental parser. |
719 | |
723 | |
720 | =over 4 |
724 | =over 4 |
721 | |
725 | |
722 | =item [void, scalar or list context] = $json->incr_parse ([$string]) |
726 | =item [void, scalar or list context] = $json->incr_parse ([$string]) |
723 | |
727 | |
… | |
… | |
761 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
765 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
762 | (such as commas). |
766 | (such as commas). |
763 | |
767 | |
764 | =item $json->incr_skip |
768 | =item $json->incr_skip |
765 | |
769 | |
766 | This will reset the state of the incremental parser and will remove the |
770 | This will reset the state of the incremental parser and will remove |
767 | parsed text from the input buffer. This is useful after C<incr_parse> |
771 | the parsed text from the input buffer so far. This is useful after |
768 | died, in which case the input buffer and incremental parser state is left |
772 | C<incr_parse> died, in which case the input buffer and incremental parser |
769 | unchanged, to skip the text parsed so far and to reset the parse state. |
773 | state is left unchanged, to skip the text parsed so far and to reset the |
|
|
774 | parse state. |
|
|
775 | |
|
|
776 | The difference to C<incr_reset> is that only text until the parse error |
|
|
777 | occured is removed. |
|
|
778 | |
|
|
779 | =item $json->incr_reset |
|
|
780 | |
|
|
781 | This completely resets the incremental parser, that is, after this call, |
|
|
782 | it will be as if the parser had never parsed anything. |
|
|
783 | |
|
|
784 | This is useful if you want to repeatedly parse JSON objects and want to |
|
|
785 | ignore any trailing data, which means you have to reset the parser after |
|
|
786 | each successful decode. |
770 | |
787 | |
771 | =back |
788 | =back |
772 | |
789 | |
773 | =head2 LIMITATIONS |
790 | =head2 LIMITATIONS |
774 | |
791 | |
… | |
… | |
1015 | Other unblessed references are generally not allowed and will cause an |
1032 | Other unblessed references are generally not allowed and will cause an |
1016 | exception to be thrown, except for references to the integers C<0> and |
1033 | exception to be thrown, except for references to the integers C<0> and |
1017 | C<1>, which get turned into C<false> and C<true> atoms in JSON. You can |
1034 | C<1>, which get turned into C<false> and C<true> atoms in JSON. You can |
1018 | also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability. |
1035 | also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability. |
1019 | |
1036 | |
1020 | encode_json [\0,JSON::XS::true] # yields [false,true] |
1037 | encode_json [\0, JSON::XS::true] # yields [false,true] |
1021 | |
1038 | |
1022 | =item JSON::XS::true, JSON::XS::false |
1039 | =item JSON::XS::true, JSON::XS::false |
1023 | |
1040 | |
1024 | These special values become JSON true and JSON false values, |
1041 | These special values become JSON true and JSON false values, |
1025 | respectively. You can also use C<\1> and C<\0> directly if you want. |
1042 | respectively. You can also use C<\1> and C<\0> directly if you want. |
… | |
… | |
1165 | when your channel for JSON transfer is not 8-bit clean or the encoding |
1182 | when your channel for JSON transfer is not 8-bit clean or the encoding |
1166 | might be mangled in between (e.g. in mail), and works because ASCII is a |
1183 | might be mangled in between (e.g. in mail), and works because ASCII is a |
1167 | proper subset of most 8-bit and multibyte encodings in use in the world. |
1184 | proper subset of most 8-bit and multibyte encodings in use in the world. |
1168 | |
1185 | |
1169 | =back |
1186 | =back |
|
|
1187 | |
|
|
1188 | |
|
|
1189 | =head2 JSON and ECMAscript |
|
|
1190 | |
|
|
1191 | JSON syntax is based on how literals are represented in javascript (the |
|
|
1192 | not-standardised predecessor of ECMAscript) which is presumably why it is |
|
|
1193 | called "JavaScript Object Notation". |
|
|
1194 | |
|
|
1195 | However, JSON is not a subset (and also not a superset of course) of |
|
|
1196 | ECMAscript (the standard) or javascript (whatever browsers actually |
|
|
1197 | implement). |
|
|
1198 | |
|
|
1199 | If you want to use javascript's C<eval> function to "parse" JSON, you |
|
|
1200 | might run into parse errors for valid JSON texts, or the resulting data |
|
|
1201 | structure might not be queryable: |
|
|
1202 | |
|
|
1203 | One of the problems is that U+2028 and U+2029 are valid characters inside |
|
|
1204 | JSON strings, but are not allowed in ECMAscript string literals, so the |
|
|
1205 | following Perl fragment will not output something that can be guaranteed |
|
|
1206 | to be parsable by javascript's C<eval>: |
|
|
1207 | |
|
|
1208 | use JSON::XS; |
|
|
1209 | |
|
|
1210 | print encode_json [chr 0x2028]; |
|
|
1211 | |
|
|
1212 | The right fix for this is to use a proper JSON parser in your javascript |
|
|
1213 | programs, and not rely on C<eval> (see for example Douglas Crockford's |
|
|
1214 | F<json2.js> parser). |
|
|
1215 | |
|
|
1216 | If this is not an option, you can, as a stop-gap measure, simply encode to |
|
|
1217 | ASCII-only JSON: |
|
|
1218 | |
|
|
1219 | use JSON::XS; |
|
|
1220 | |
|
|
1221 | print JSON::XS->new->ascii->encode ([chr 0x2028]); |
|
|
1222 | |
|
|
1223 | Note that this will enlarge the resulting JSON text quite a bit if you |
|
|
1224 | have many non-ASCII characters. You might be tempted to run some regexes |
|
|
1225 | to only escape U+2028 and U+2029, e.g.: |
|
|
1226 | |
|
|
1227 | # DO NOT USE THIS! |
|
|
1228 | my $json = JSON::XS->new->utf8->encode ([chr 0x2028]); |
|
|
1229 | $json =~ s/\xe2\x80\xa8/\\u2028/g; # escape U+2028 |
|
|
1230 | $json =~ s/\xe2\x80\xa9/\\u2029/g; # escape U+2029 |
|
|
1231 | print $json; |
|
|
1232 | |
|
|
1233 | Note that I<this is a bad idea>: the above only works for U+2028 and |
|
|
1234 | U+2029 and thus only for fully ECMAscript-compliant parsers. Many existing |
|
|
1235 | javascript implementations, however, have issues with other characters as |
|
|
1236 | well - using C<eval> naively simply I<will> cause problems. |
|
|
1237 | |
|
|
1238 | Another problem is that some javascript implementations reserve |
|
|
1239 | some property names for their own purposes (which probably makes |
|
|
1240 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
|
|
1241 | C<__proto__> property name for it's own purposes. |
|
|
1242 | |
|
|
1243 | If that is a problem, you could parse try to filter the resulting JSON |
|
|
1244 | output for these property strings, e.g.: |
|
|
1245 | |
|
|
1246 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
|
|
1247 | |
|
|
1248 | This works because C<__proto__> is not valid outside of strings, so every |
|
|
1249 | occurence of C<"__proto__"\s*:> must be a string used as property name. |
|
|
1250 | |
|
|
1251 | If you know of other incompatibilities, please let me know. |
1170 | |
1252 | |
1171 | |
1253 | |
1172 | =head2 JSON and YAML |
1254 | =head2 JSON and YAML |
1173 | |
1255 | |
1174 | You often hear that JSON is a subset of YAML. This is, however, a mass |
1256 | You often hear that JSON is a subset of YAML. This is, however, a mass |