… | |
… | |
81 | |
81 | |
82 | package JSON::XS; |
82 | package JSON::XS; |
83 | |
83 | |
84 | use strict; |
84 | use strict; |
85 | |
85 | |
86 | our $VERSION = '1.4'; |
86 | our $VERSION = '1.5'; |
87 | our @ISA = qw(Exporter); |
87 | our @ISA = qw(Exporter); |
88 | |
88 | |
89 | our @EXPORT = qw(to_json from_json); |
89 | our @EXPORT = qw(to_json from_json); |
90 | |
90 | |
91 | use Exporter; |
91 | use Exporter; |
… | |
… | |
278 | |
278 | |
279 | Example, space_before and indent disabled, space_after enabled: |
279 | Example, space_before and indent disabled, space_after enabled: |
280 | |
280 | |
281 | {"key": "value"} |
281 | {"key": "value"} |
282 | |
282 | |
|
|
283 | =item $json = $json->relaxed ([$enable]) |
|
|
284 | |
|
|
285 | If C<$enable> is true (or missing), then C<decode> will accept some |
|
|
286 | extensions to normal JSON syntax (see below). C<encode> will not be |
|
|
287 | affected in anyway. I<Be aware that this option makes you accept invalid |
|
|
288 | JSON texts as if they were valid!>. I suggest only to use this option to |
|
|
289 | parse application-specific files written by humans (configuration files, |
|
|
290 | resource files etc.) |
|
|
291 | |
|
|
292 | If C<$enable> is false (the default), then C<decode> will only accept |
|
|
293 | valid JSON texts. |
|
|
294 | |
|
|
295 | Currently accepted extensions are: |
|
|
296 | |
|
|
297 | =over 4 |
|
|
298 | |
|
|
299 | =item * list items can have an end-comma |
|
|
300 | |
|
|
301 | JSON I<separates> array elements and key-value pairs with commas. This |
|
|
302 | can be annoying if you write JSON texts manually and want to be able to |
|
|
303 | quickly append elements, so this extension accepts comma at the end of |
|
|
304 | such items not just between them: |
|
|
305 | |
|
|
306 | [ |
|
|
307 | 1, |
|
|
308 | 2, <- this comma not normally allowed |
|
|
309 | ] |
|
|
310 | { |
|
|
311 | "k1": "v1", |
|
|
312 | "k2": "v2", <- this comma not normally allowed |
|
|
313 | } |
|
|
314 | |
|
|
315 | =back |
|
|
316 | |
283 | =item $json = $json->canonical ([$enable]) |
317 | =item $json = $json->canonical ([$enable]) |
284 | |
318 | |
285 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
319 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
286 | by sorting their keys. This is adding a comparatively high overhead. |
320 | by sorting their keys. This is adding a comparatively high overhead. |
287 | |
321 | |
… | |
… | |
348 | enabled by this setting. |
382 | enabled by this setting. |
349 | |
383 | |
350 | If C<$enable> is false, then the C<allow_blessed> setting will decide what |
384 | If C<$enable> is false, then the C<allow_blessed> setting will decide what |
351 | to do when a blessed object is found. |
385 | to do when a blessed object is found. |
352 | |
386 | |
353 | =item $json = $json->filter_json_object ([$coderef]) |
387 | =item $json = $json->filter_json_object ([$coderef->($hashref)]) |
354 | |
388 | |
355 | When C<$coderef> is specified, it will be called from C<decode> each |
389 | When C<$coderef> is specified, it will be called from C<decode> each |
356 | time it decodes a JSON object. The only argument is a reference to the |
390 | time it decodes a JSON object. The only argument is a reference to the |
357 | newly-created hash. If the code references returns a single scalar (which |
391 | newly-created hash. If the code references returns a single scalar (which |
358 | need not be a reference), this value (i.e. a copy of that scalar to avoid |
392 | need not be a reference), this value (i.e. a copy of that scalar to avoid |
359 | aliasing) is inserted into the deserialised data structure. If it returns |
393 | aliasing) is inserted into the deserialised data structure. If it returns |
360 | an empty list (NOTE: I<not> C<undef>, which is a valid scalar), the |
394 | an empty list (NOTE: I<not> C<undef>, which is a valid scalar), the |
361 | original deserialised hash will be inserted. This setting can slow down |
395 | original deserialised hash will be inserted. This setting can slow down |
362 | decoding considerably. |
396 | decoding considerably. |
363 | |
397 | |
364 | When C<$coderef> is omitted or undefined, C<decode> will not change the |
398 | When C<$coderef> is omitted or undefined, any existing callback will |
365 | deserialised hash in any way. This is maximally fast. |
399 | be removed and C<decode> will not change the deserialised hash in any |
|
|
400 | way. |
366 | |
401 | |
367 | Example, convert all JSON objects into the integer 5: |
402 | Example, convert all JSON objects into the integer 5: |
368 | |
403 | |
369 | my $js = JSON::XS->new->filter_json_object (sub { 5 }); |
404 | my $js = JSON::XS->new->filter_json_object (sub { 5 }); |
370 | # returns [5] |
405 | # returns [5] |
371 | $js->decode ('[{}]') |
406 | $js->decode ('[{}]') |
372 | # throw an exception because allow_nonref is not enabled: |
407 | # throw an exception because allow_nonref is not enabled |
|
|
408 | # so a lone 5 is not allowed. |
373 | $js->decode ('{"a":1, "b":2}'); |
409 | $js->decode ('{"a":1, "b":2}'); |
374 | |
410 | |
375 | =item $json = $json->filter_json_single_key_object ([$coderef]) |
411 | =item $json = $json->filter_json_single_key_object ($key [=> $coderef->($value)]) |
376 | |
412 | |
377 | Works like C<filter_json_object>, but is only called for JSON objects |
413 | Works remotely similar to C<filter_json_object>, but is only called for |
378 | having only a single key. |
414 | JSON objects having a single key named C<$key>. |
379 | |
415 | |
380 | This C<$coderef> is called before the one specified via |
416 | This C<$coderef> is called before the one specified via |
381 | C<filter_json_object>, if any. If it returns something, that will be |
417 | C<filter_json_object>, if any. It gets passed the single value in the JSON |
382 | inserted into the data structure. If it returns nothing, the callback |
418 | object. If it returns a single value, it will be inserted into the data |
383 | from C<filter_json_object> will be called next. If you want to force |
419 | structure. If it returns nothing (not even C<undef> but the empty list), |
384 | insertion of single-key objects even in the presence of a mutating |
420 | the callback from C<filter_json_object> will be called next, as if no |
385 | C<filter_json_object> callback, simply return the passed hash. |
421 | single-key callback were specified. |
|
|
422 | |
|
|
423 | If C<$coderef> is omitted or undefined, the corresponding callback will be |
|
|
424 | disabled. There can only ever be one callback for a given key. |
386 | |
425 | |
387 | As this callback gets called less often then the C<filter_json_object> |
426 | As this callback gets called less often then the C<filter_json_object> |
388 | one, decoding speed will not usually suffer as much. Therefore, single-key |
427 | one, decoding speed will not usually suffer as much. Therefore, single-key |
389 | objects make excellent targets to serialise Perl objects into, especially |
428 | objects make excellent targets to serialise Perl objects into, especially |
390 | as single-key JSON objects are as close to the type-tagged value concept |
429 | as single-key JSON objects are as close to the type-tagged value concept |
… | |
… | |
401 | into the corresponding C<< $WIDGET{<id>} >> object: |
440 | into the corresponding C<< $WIDGET{<id>} >> object: |
402 | |
441 | |
403 | # return whatever is in $WIDGET{5}: |
442 | # return whatever is in $WIDGET{5}: |
404 | JSON::XS |
443 | JSON::XS |
405 | ->new |
444 | ->new |
406 | ->filter_json_single_key_object (sub { |
445 | ->filter_json_single_key_object (__widget__ => sub { |
407 | exists $_[0]{__widget__} |
|
|
408 | ? $WIDGET{ $_[0]{__widget__} } |
446 | $WIDGET{ $_[0] } |
409 | : () |
|
|
410 | }) |
447 | }) |
411 | ->decode ('{"__widget__": 5') |
448 | ->decode ('{"__widget__": 5') |
412 | |
449 | |
413 | # this can be used with a TO_JSON method in some "widget" class |
450 | # this can be used with a TO_JSON method in some "widget" class |
414 | # for serialisation to json: |
451 | # for serialisation to json: |
… | |
… | |
550 | are represented by the same codepoints in the Perl string, so no manual |
587 | are represented by the same codepoints in the Perl string, so no manual |
551 | decoding is necessary. |
588 | decoding is necessary. |
552 | |
589 | |
553 | =item number |
590 | =item number |
554 | |
591 | |
555 | A JSON number becomes either an integer or numeric (floating point) |
592 | A JSON number becomes either an integer, numeric (floating point) or |
556 | scalar in perl, depending on its range and any fractional parts. On the |
593 | string scalar in perl, depending on its range and any fractional parts. On |
557 | Perl level, there is no difference between those as Perl handles all the |
594 | the Perl level, there is no difference between those as Perl handles all |
558 | conversion details, but an integer may take slightly less memory and might |
595 | the conversion details, but an integer may take slightly less memory and |
559 | represent more values exactly than (floating point) numbers. |
596 | might represent more values exactly than (floating point) numbers. |
|
|
597 | |
|
|
598 | If the number consists of digits only, JSON::XS will try to represent |
|
|
599 | it as an integer value. If that fails, it will try to represent it as |
|
|
600 | a numeric (floating point) value if that is possible without loss of |
|
|
601 | precision. Otherwise it will preserve the number as a string value. |
|
|
602 | |
|
|
603 | Numbers containing a fractional or exponential part will always be |
|
|
604 | represented as numeric (floating point) values, possibly at a loss of |
|
|
605 | precision. |
|
|
606 | |
|
|
607 | This might create round-tripping problems as numbers might become strings, |
|
|
608 | but as Perl is typeless there is no other way to do it. |
560 | |
609 | |
561 | =item true, false |
610 | =item true, false |
562 | |
611 | |
563 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
612 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
564 | respectively. They are overloaded to act almost exactly like the numbers |
613 | respectively. They are overloaded to act almost exactly like the numbers |
… | |
… | |
875 | still relatively early in its development. If you keep reporting bugs they |
924 | still relatively early in its development. If you keep reporting bugs they |
876 | will be fixed swiftly, though. |
925 | will be fixed swiftly, though. |
877 | |
926 | |
878 | =cut |
927 | =cut |
879 | |
928 | |
880 | our $true = do { bless \(my $dummy = "1"), "JSON::XS::Boolean" }; |
929 | our $true = do { bless \(my $dummy = 1), "JSON::XS::Boolean" }; |
881 | our $false = do { bless \(my $dummy = "0"), "JSON::XS::Boolean" }; |
930 | our $false = do { bless \(my $dummy = 0), "JSON::XS::Boolean" }; |
882 | |
931 | |
883 | sub true() { $true } |
932 | sub true() { $true } |
884 | sub false() { $false } |
933 | sub false() { $false } |
885 | |
934 | |
886 | sub is_bool($) { |
935 | sub is_bool($) { |