… | |
… | |
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 | overridden) with no overhead due to emulation (by inheriting 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 it and |
46 | require a C compiler when that is a problem. |
46 | doesn't require a C compiler when that is a problem. |
47 | |
47 | |
48 | As this is the n-th-something JSON module on CPAN, what was the reason |
48 | As this is the n-th-something JSON module on CPAN, what was the reason |
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 |
… | |
… | |
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 = 3.02; |
106 | our $VERSION = 3.04; |
107 | our @ISA = qw(Exporter); |
107 | our @ISA = qw(Exporter); |
108 | |
108 | |
109 | our @EXPORT = qw(encode_json decode_json); |
109 | our @EXPORT = qw(encode_json decode_json); |
110 | |
110 | |
111 | use Exporter; |
111 | use Exporter; |
… | |
… | |
748 | C<incr_skip> to skip the erroneous part). This is the most common way of |
748 | C<incr_skip> to skip the erroneous part). This is the most common way of |
749 | using the method. |
749 | using the method. |
750 | |
750 | |
751 | And finally, in list context, it will try to extract as many objects |
751 | And finally, in list context, it will try to extract as many objects |
752 | from the stream as it can find and return them, or the empty list |
752 | from the stream as it can find and return them, or the empty list |
753 | otherwise. For this to work, there must be no separators between the JSON |
753 | otherwise. For this to work, there must be no separators (other than |
754 | objects or arrays, instead they must be concatenated back-to-back. If |
754 | whitespace) between the JSON objects or arrays, instead they must be |
755 | an error occurs, an exception will be raised as in the scalar context |
755 | concatenated back-to-back. If an error occurs, an exception will be |
756 | case. Note that in this case, any previously-parsed JSON texts will be |
756 | raised as in the scalar context case. Note that in this case, any |
757 | lost. |
757 | previously-parsed JSON texts will be lost. |
758 | |
758 | |
759 | Example: Parse some JSON arrays/objects in a given string and return |
759 | Example: Parse some JSON arrays/objects in a given string and return |
760 | them. |
760 | them. |
761 | |
761 | |
762 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
762 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
… | |
… | |
768 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
768 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
769 | all other circumstances you must not call this function (I mean it. |
769 | all other circumstances you must not call this function (I mean it. |
770 | although in simple tests it might actually work, it I<will> fail under |
770 | although in simple tests it might actually work, it I<will> fail under |
771 | real world conditions). As a special exception, you can also call this |
771 | real world conditions). As a special exception, you can also call this |
772 | method before having parsed anything. |
772 | method before having parsed anything. |
|
|
773 | |
|
|
774 | That means you can only use this function to look at or manipulate text |
|
|
775 | before or after complete JSON objects, not while the parser is in the |
|
|
776 | middle of parsing a JSON object. |
773 | |
777 | |
774 | This function is useful in two cases: a) finding the trailing text after a |
778 | This function is useful in two cases: a) finding the trailing text after a |
775 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
779 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
776 | (such as commas). |
780 | (such as commas). |
777 | |
781 | |
… | |
… | |
1608 | |
1612 | |
1609 | =head1 INTEROPERABILITY WITH OTHER MODULES |
1613 | =head1 INTEROPERABILITY WITH OTHER MODULES |
1610 | |
1614 | |
1611 | C<JSON::XS> uses the L<Types::Serialiser> module to provide boolean |
1615 | C<JSON::XS> uses the L<Types::Serialiser> module to provide boolean |
1612 | constants. That means that the JSON true and false values will be |
1616 | constants. That means that the JSON true and false values will be |
1613 | comaptible to true and false values of iother modules that do the same, |
1617 | comaptible to true and false values of other modules that do the same, |
1614 | such as L<JSON::PP> and L<CBOR::XS>. |
1618 | such as L<JSON::PP> and L<CBOR::XS>. |
1615 | |
1619 | |
1616 | |
1620 | |
1617 | =head1 INTEROPERABILITY WITH OTHER JSON DECODERS |
1621 | =head1 INTEROPERABILITY WITH OTHER JSON DECODERS |
1618 | |
1622 | |
… | |
… | |
1635 | |
1639 | |
1636 | When you use C<allow_tags> to use the extended (and also nonstandard and |
1640 | When you use C<allow_tags> to use the extended (and also nonstandard and |
1637 | invalid) JSON syntax for serialised objects, and you still want to decode |
1641 | invalid) JSON syntax for serialised objects, and you still want to decode |
1638 | the generated When you want to serialise objects, you can run a regex |
1642 | the generated When you want to serialise objects, you can run a regex |
1639 | to replace the tagged syntax by standard JSON arrays (it only works for |
1643 | to replace the tagged syntax by standard JSON arrays (it only works for |
1640 | "normal" packagesnames without comma, newlines or single colons). First, |
1644 | "normal" package names without comma, newlines or single colons). First, |
1641 | the readable Perl version: |
1645 | the readable Perl version: |
1642 | |
1646 | |
1643 | # if your FREEZE methods return no values, you need this replace first: |
1647 | # if your FREEZE methods return no values, you need this replace first: |
1644 | $json =~ s/\( \s* (" (?: [^\\":,]+|\\.|::)* ") \s* \) \s* \[\s*\]/[$1]/gx; |
1648 | $json =~ s/\( \s* (" (?: [^\\":,]+|\\.|::)* ") \s* \) \s* \[\s*\]/[$1]/gx; |
1645 | |
1649 | |
… | |
… | |
1681 | Since this module was written, Google has written a new JSON RFC, RFC 7159 |
1685 | Since this module was written, Google has written a new JSON RFC, RFC 7159 |
1682 | (and RFC7158). Unfortunately, this RFC breaks compatibility with both the |
1686 | (and RFC7158). Unfortunately, this RFC breaks compatibility with both the |
1683 | original JSON specification on www.json.org and RFC4627. |
1687 | original JSON specification on www.json.org and RFC4627. |
1684 | |
1688 | |
1685 | As far as I can see, you can get partial compatibility when parsing by |
1689 | As far as I can see, you can get partial compatibility when parsing by |
1686 | using C<< ->allow_nonref >>. However, consider thew security implications |
1690 | using C<< ->allow_nonref >>. However, consider the security implications |
1687 | of doing so. |
1691 | of doing so. |
1688 | |
1692 | |
1689 | I haven't decided yet when to break compatibility with RFC4627 by default |
1693 | I haven't decided yet when to break compatibility with RFC4627 by default |
1690 | (and potentially leave applications insecure) and change the default to |
1694 | (and potentially leave applications insecure) and change the default to |
1691 | follow RFC7159, but application authors are well advised to call C<< |
1695 | follow RFC7159, but application authors are well advised to call C<< |
1692 | ->allow_nonref(0) >> even if this is the current default, if they cannot |
1696 | ->allow_nonref(0) >> even if this is the current default, if they cannot |
1693 | handle non-reference values, in preparation for the day when the4 default |
1697 | handle non-reference values, in preparation for the day when the default |
1694 | will change. |
1698 | will change. |
1695 | |
1699 | |
1696 | |
1700 | |
1697 | =head1 THREADS |
1701 | =head1 (I-)THREADS |
1698 | |
1702 | |
1699 | This module is I<not> guaranteed to be thread safe and there are no |
1703 | This module is I<not> guaranteed to be ithread (or MULTIPLICITY-) safe |
1700 | plans to change this until Perl gets thread support (as opposed to the |
1704 | and there are no plans to change this. Note that perl's builtin so-called |
1701 | horribly slow so-called "threads" which are simply slow and bloated |
1705 | theeads/ithreads are officially deprecated and should not be used. |
1702 | process simulations - use fork, it's I<much> faster, cheaper, better). |
|
|
1703 | |
|
|
1704 | (It might actually work, but you have been warned). |
|
|
1705 | |
1706 | |
1706 | |
1707 | |
1707 | =head1 THE PERILS OF SETLOCALE |
1708 | =head1 THE PERILS OF SETLOCALE |
1708 | |
1709 | |
1709 | Sometimes people avoid the Perl locale support and directly call the |
1710 | Sometimes people avoid the Perl locale support and directly call the |