… | |
… | |
64 | so, and even documents what "correct" means. |
64 | so, and even documents what "correct" means. |
65 | |
65 | |
66 | =item * round-trip integrity |
66 | =item * round-trip integrity |
67 | |
67 | |
68 | When you serialise a perl data structure using only data types supported |
68 | When you serialise a perl data structure using only data types supported |
69 | by JSON, the deserialised data structure is identical on the Perl level. |
69 | by JSON and Perl, the deserialised data structure is identical on the Perl |
70 | (e.g. the string "2.0" doesn't suddenly become "2" just because it looks |
70 | level. (e.g. the string "2.0" doesn't suddenly become "2" just because |
71 | like a number). There minor I<are> exceptions to this, read the MAPPING |
71 | it looks like a number). There I<are> minor exceptions to this, read the |
72 | section below to learn about those. |
72 | MAPPING section below to learn about those. |
73 | |
73 | |
74 | =item * strict checking of JSON correctness |
74 | =item * strict checking of JSON correctness |
75 | |
75 | |
76 | There is no guessing, no generating of illegal JSON texts by default, |
76 | There is no guessing, no generating of illegal JSON texts by default, |
77 | and only JSON is accepted as input by default (the latter is a security |
77 | and only JSON is accepted as input by default (the latter is a security |
… | |
… | |
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 = '2.28'; |
106 | our $VERSION = '2.29'; |
107 | our @ISA = qw(Exporter); |
107 | our @ISA = qw(Exporter); |
108 | |
108 | |
109 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
109 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
110 | |
110 | |
111 | sub to_json($) { |
111 | sub to_json($) { |
… | |
… | |
751 | objects or arrays, instead they must be concatenated back-to-back. If |
751 | objects or arrays, instead they must be concatenated back-to-back. If |
752 | an error occurs, an exception will be raised as in the scalar context |
752 | an error occurs, an exception will be raised as in the scalar context |
753 | case. Note that in this case, any previously-parsed JSON texts will be |
753 | case. Note that in this case, any previously-parsed JSON texts will be |
754 | lost. |
754 | lost. |
755 | |
755 | |
|
|
756 | Example: Parse some JSON arrays/objects in a given string and return |
|
|
757 | them. |
|
|
758 | |
|
|
759 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
|
|
760 | |
756 | =item $lvalue_string = $json->incr_text |
761 | =item $lvalue_string = $json->incr_text |
757 | |
762 | |
758 | This method returns the currently stored JSON fragment as an lvalue, that |
763 | This method returns the currently stored JSON fragment as an lvalue, that |
759 | is, you can manipulate it. This I<only> works when a preceding call to |
764 | is, you can manipulate it. This I<only> works when a preceding call to |
760 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
765 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
… | |
… | |
989 | Numbers containing a fractional or exponential part will always be |
994 | Numbers containing a fractional or exponential part will always be |
990 | represented as numeric (floating point) values, possibly at a loss of |
995 | represented as numeric (floating point) values, possibly at a loss of |
991 | precision (in which case you might lose perfect roundtripping ability, but |
996 | precision (in which case you might lose perfect roundtripping ability, but |
992 | the JSON number will still be re-encoded as a JSON number). |
997 | the JSON number will still be re-encoded as a JSON number). |
993 | |
998 | |
|
|
999 | Note that precision is not accuracy - binary floating point values cannot |
|
|
1000 | represent most decimal fractions exactly, and when converting from and to |
|
|
1001 | floating point, JSON::XS only guarantees precision up to but not including |
|
|
1002 | the leats significant bit. |
|
|
1003 | |
994 | =item true, false |
1004 | =item true, false |
995 | |
1005 | |
996 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
1006 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
997 | respectively. They are overloaded to act almost exactly like the numbers |
1007 | respectively. They are overloaded to act almost exactly like the numbers |
998 | C<1> and C<0>. You can check whether a scalar is a JSON boolean by using |
1008 | C<1> and C<0>. You can check whether a scalar is a JSON boolean by using |
… | |
… | |
1084 | $x *= 1; # same thing, the choice is yours. |
1094 | $x *= 1; # same thing, the choice is yours. |
1085 | |
1095 | |
1086 | You can not currently force the type in other, less obscure, ways. Tell me |
1096 | You can not currently force the type in other, less obscure, ways. Tell me |
1087 | if you need this capability (but don't forget to explain why it's needed |
1097 | if you need this capability (but don't forget to explain why it's needed |
1088 | :). |
1098 | :). |
|
|
1099 | |
|
|
1100 | Note that numerical precision has the same meaning as under Perl (so |
|
|
1101 | binary to decimal conversion follows the same rules as in Perl, which |
|
|
1102 | can differ to other languages). Also, your perl interpreter might expose |
|
|
1103 | extensions to the floating point numbers of your platform, such as |
|
|
1104 | infinities or NaN's - these cannot be represented in JSON, and it is an |
|
|
1105 | error to pass those in. |
1089 | |
1106 | |
1090 | =back |
1107 | =back |
1091 | |
1108 | |
1092 | |
1109 | |
1093 | =head1 ENCODING/CODESET FLAG NOTES |
1110 | =head1 ENCODING/CODESET FLAG NOTES |