Lines Matching refs:PERL
666 has since Perl 5.14 been a core module. For this reason,
672 =item * L<http://perl5.git.perlperl.git>
694 This module converts Perl data structures to JSON and vice versa using either
699 JSON::PP is a pure-Perl module which is bundled in this distribution and
724 Even though there are limitations, this feature is available since Perl version 5.6.
726 JSON::XS requires Perl 5.8.2 (but works correctly in 5.8.8 or later), so in older versions
727 C<JSON> should call JSON::PP as the backend which can be used since Perl 5.005.
729 With Perl 5.8.x JSON::PP works, but from 5.8.0 to 5.8.2, because of a Perl side problem,
733 See also to L<JSON::XS/A FEW NOTES ON UNICODE AND PERL>
739 When you serialise a perl data structure using only data types supported
740 by JSON and Perl, the deserialised data structure is identical on the Perl
761 it is very slow as pure-Perl.
787 Converts the given Perl data structure to a UTF-8 encoded, binary string.
810 Converts the given Perl data structure to a json string.
828 If you want to write a modern perl code which communicates to outer world,
854 If you want to write a modern perl code which communicates to outer world,
863 and are also used to represent JSON C<true> and C<false> in Perl strings.
880 Perl.
884 This section supposes that your perl version is 5.8 or later.
938 for some reason, then its characters are regarded as B<latin1> for perl
992 This feature depends on the used Perl version and environment.
1012 => ["\x{89}\\u0abc"] # (perl syntax, U+abc escaped, U+89 not)
1180 pairs in the order Perl stores them (which will likely change between runs
1186 as key-value pairs have no inherent ordering in Perl.
1262 methods called by the Perl core (== not by the user of the object) are
1342 objects make excellent targets to serialise Perl objects into, especially
1346 like a serialised Perl hash.
1388 if possible: perl stores strings internally either in an encoding called
1390 space in general (and some buggy Perl or C code might even rely on that
1405 or decoding. If a higher nesting level is detected in JSON text or a Perl
1423 'Deep recursion on subroutine' at the perl runtime phase.
1448 Converts the given Perl data structure (a simple scalar or a reference
1452 Perl values (e.g. C<undef>) become JSON C<null> values.
1462 JSON numbers and strings become simple Perl scalars. JSON arrays become
1463 Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes
1584 In Perl 5.005, C<lvalue> attribute is not available.
1672 the big integer Perl cannot handle as integer into a L<Math::BigInt>
1746 =head2 JSON -> PERL
1752 A JSON object becomes a reference to a hash in Perl. No ordering of object
1757 A JSON array becomes a reference to an array in Perl.
1761 A JSON string becomes a string scalar in Perl - Unicode codepoints in JSON
1762 are represented by the same codepoints in the Perl string, so no manual
1768 string scalar in perl, depending on its range and any fractional parts. On
1769 the Perl level, there is no difference between those as Perl handles all
1818 A JSON null atom becomes C<undef> in Perl.
1825 =head2 PERL -> JSON
1827 The mapping from Perl to JSON is slightly more difficult, as Perl is a
1829 a Perl value.
1835 Perl hash references become JSON objects. As there is no inherent ordering
1850 Perl array references become JSON arrays.
1887 Simple Perl scalars (any scalar that is not a reference) are the most
1909 print $x; # perl does it for you, too, quite often
1919 Note that numerical precision has the same meaning as under Perl (so
1920 binary to decimal conversion follows the same rules as in Perl, which
1921 can differ to other languages). Also, your perl interpreter might expose
2046 Non Perl-style name C<jsonToObj> and C<objToJson> are obsoleted
2084 Perl implementation of JSON-RPC protocol - C<JSONRPC >, C<JSONRPC::Transport::HTTP>
2230 See to L<JSON::XS/A FEW NOTES ON UNICODE AND PERL>.
2289 it under the same terms as Perl itself.
