lib/JSON/PP.pm

315 ### Perl => JSON
683 # JSON => Perl
1729 JSON::PP - JSON::XS compatible pure-Perl module.
1770 JSON::PP has been in the Perl core since Perl 5.14, mainly for
1782 Converts the given Perl data structure to a UTF-8 encoded, binary string
1811 and are also used to represent JSON C<true> and C<false> in Perl strings.
1817 Perl.
2084 pairs in the order Perl stores them (which will likely change between runs
2091 as key-value pairs have no inherent ordering in Perl.
2116 Example, encode a Perl scalar as JSON value without enabled C<allow_nonref>,
2175 methods called by the Perl core (== not by the user of the object) are
2292 objects make excellent targets to serialise Perl objects into, especially
2296 like a serialised Perl hash.
2348 or decoding. If a higher nesting level is detected in JSON text or a Perl
2386 Converts the given Perl value or data structure to its JSON
2465 big integers Perl cannot handle as integer into L<Math::BigInt>
2538 then the argument will be passed to Perl's C<sort> built-in function.
2574 Perl data structure in memory at one time, it does allow you to parse a
2679 This section describes how JSON::PP maps Perl values to JSON values and
2685 lowercase I<perl> refers to the Perl interpreter, while uppercase I<Perl>
2686 refers to the abstract Perl language itself.
2694 A JSON object becomes a reference to a hash in Perl. No ordering of object
2699 A JSON array becomes a reference to an array in Perl.
2703 A JSON string becomes a string scalar in Perl - Unicode codepoints in JSON
2704 are represented by the same codepoints in the Perl string, so no manual
2711 the Perl level, there is no difference between those as Perl handles all
2746 A JSON null atom becomes C<undef> in Perl.
2768 The mapping from Perl to JSON is slightly more difficult, as Perl is a
2770 a Perl value.
2776 Perl hash references become JSON objects. As there is no inherent
2787 Perl array references become JSON arrays.
2816 Simple Perl scalars (any scalar that is not a reference) are the most
2859 Note that numerical precision has the same meaning as under Perl (so
2860 binary to decimal conversion follows the same rules as in Perl, which
2884 As JSON cannot directly represent Perl objects, you have to choose between
2891 What happens when C<JSON::PP> encounters a Perl object depends on the
2972 to load the package as a Perl module). If there is no such method, the
2981 any Perl scalar, you might have to enable the C<allow_nonref> setting to
3030 respectively (to Perl, these are the same thing in strings unless you do
3037 to UTF-8 encode your data first and have Perl encode it another time).
3048 will get a Unicode string in Perl, enabled means you get an UTF-8 encoded
3049 octet/binary string in Perl.
3061 the same thing as an ASCII string in Perl).
3140 it under the same terms as Perl itself.