ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/JSON-XS/XS.pm
(Generate patch)

Comparing JSON-XS/XS.pm (file contents):
Revision 1.134 by root, Mon Feb 21 15:38:06 2011 UTC vs.
Revision 1.145 by root, Tue Oct 29 00:06:40 2013 UTC

… …
83this module usually compares favourably in terms of speed, too. 83this module usually compares favourably in terms of speed, too.
84 84
85=item * simple to use 85=item * simple to use
86 86
87This module has both a simple functional interface as well as an object 87This module has both a simple functional interface as well as an object
88oriented interface interface. 88oriented interface.
89 89
90=item * reasonably versatile output formats 90=item * reasonably versatile output formats
91 91
92You can choose between the most compact guaranteed-single-line format 92You can choose between the most compact guaranteed-single-line format
93possible (nice for simple line-based protocols), a pure-ASCII format 93possible (nice for simple line-based protocols), a pure-ASCII format
… …
101 101
102package JSON::XS; 102package JSON::XS;
103 103
104use common::sense; 104use common::sense;
105 105
106our $VERSION = '2.3'; 106our $VERSION = '3.0';
107our @ISA = qw(Exporter); 107our @ISA = qw(Exporter);
108 108
109our @EXPORT = qw(encode_json decode_json to_json from_json); 109our @EXPORT = qw(encode_json decode_json);
110
111sub to_json($) {
112 require Carp;
113 Carp::croak ("JSON::XS::to_json has been renamed to encode_json, either downgrade to pre-2.0 versions of JSON::XS or rename the call");
114}
115
116sub from_json($) {
117 require Carp;
118 Carp::croak ("JSON::XS::from_json has been renamed to decode_json, either downgrade to pre-2.0 versions of JSON::XS or rename the call");
119}
120 110
121use Exporter; 111use Exporter;
122use XSLoader; 112use XSLoader;
113
114use Types::Serialiser ();
123 115
124=head1 FUNCTIONAL INTERFACE 116=head1 FUNCTIONAL INTERFACE
125 117
126The following convenience methods are provided by this module. They are 118The following convenience methods are provided by this module. They are
127exported by default: 119exported by default:
… …
148This function call is functionally identical to: 140This function call is functionally identical to:
149 141
150 $perl_scalar = JSON::XS->new->utf8->decode ($json_text) 142 $perl_scalar = JSON::XS->new->utf8->decode ($json_text)
151 143
152Except being faster. 144Except being faster.
153
154=item $is_boolean = JSON::XS::is_bool $scalar
155
156Returns true if the passed scalar represents either JSON::XS::true or
157JSON::XS::false, two constants that act like C<1> and C<0>, respectively
158and are used to represent JSON C<true> and C<false> values in Perl.
159
160See MAPPING, below, for more information on how JSON values are mapped to
161Perl.
162 145
163=back 146=back
164 147
165 148
166=head1 A FEW NOTES ON UNICODE AND PERL 149=head1 A FEW NOTES ON UNICODE AND PERL
… …
432If C<$enable> is true (or missing), then the C<encode> method will output JSON objects 415If C<$enable> is true (or missing), then the C<encode> method will output JSON objects
433by sorting their keys. This is adding a comparatively high overhead. 416by sorting their keys. This is adding a comparatively high overhead.
434 417
435If C<$enable> is false, then the C<encode> method will output key-value 418If C<$enable> is false, then the C<encode> method will output key-value
436pairs in the order Perl stores them (which will likely change between runs 419pairs in the order Perl stores them (which will likely change between runs
437of the same script). 420of the same script, and can change even within the same run from 5.18
421onwards).
438 422
439This option is useful if you want the same data structure to be encoded as 423This option is useful if you want the same data structure to be encoded as
440the same JSON text (given the same overall settings). If it is disabled, 424the same JSON text (given the same overall settings). If it is disabled,
441the same hash might be encoded differently even if contains the same data, 425the same hash might be encoded differently even if contains the same data,
442as key-value pairs have no inherent ordering in Perl. 426as key-value pairs have no inherent ordering in Perl.
… …
666 650
667See SECURITY CONSIDERATIONS, below, for more info on why this is useful. 651See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
668 652
669=item $json_text = $json->encode ($perl_scalar) 653=item $json_text = $json->encode ($perl_scalar)
670 654
671Converts the given Perl data structure (a simple scalar or a reference 655Converts the given Perl value or data structure to its JSON
672to a hash or array) to its JSON representation. Simple scalars will be 656representation. Croaks on error.
673converted into JSON string or number sequences, while references to arrays
674become JSON arrays and references to hashes become JSON objects. Undefined
675Perl values (e.g. C<undef>) become JSON C<null> values. Neither C<true>
676nor C<false> values will be generated.
677 657
678=item $perl_scalar = $json->decode ($json_text) 658=item $perl_scalar = $json->decode ($json_text)
679 659
680The opposite of C<encode>: expects a JSON text and tries to parse it, 660The opposite of C<encode>: expects a JSON text and tries to parse it,
681returning the resulting simple scalar or reference. Croaks on error. 661returning the resulting simple scalar or reference. Croaks on error.
682
683JSON numbers and strings become simple Perl scalars. JSON arrays become
684Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes
685C<1>, C<false> becomes C<0> and C<null> becomes C<undef>.
686 662
687=item ($perl_scalar, $characters) = $json->decode_prefix ($json_text) 663=item ($perl_scalar, $characters) = $json->decode_prefix ($json_text)
688 664
689This works like the C<decode> method, but instead of raising an exception 665This works like the C<decode> method, but instead of raising an exception
690when there is trailing garbage after the first JSON object, it will 666when there is trailing garbage after the first JSON object, it will
691silently stop parsing there and return the number of characters consumed 667silently stop parsing there and return the number of characters consumed
692so far. 668so far.
693 669
694This is useful if your JSON texts are not delimited by an outer protocol 670This is useful if your JSON texts are not delimited by an outer protocol
695(which is not the brightest thing to do in the first place) and you need
696to know where the JSON text ends. 671and you need to know where the JSON text ends.
697 672
698 JSON::XS->new->decode_prefix ("[1] the tail") 673 JSON::XS->new->decode_prefix ("[1] the tail")
699 => ([], 3) 674 => ([], 3)
700 675
701=back 676=back
… …
740 715
741If the method is called in scalar context, then it will try to extract 716If the method is called in scalar context, then it will try to extract
742exactly I<one> JSON object. If that is successful, it will return this 717exactly I<one> JSON object. If that is successful, it will return this
743object, otherwise it will return C<undef>. If there is a parse error, 718object, otherwise it will return C<undef>. If there is a parse error,
744this method will croak just as C<decode> would do (one can then use 719this method will croak just as C<decode> would do (one can then use
745C<incr_skip> to skip the errornous part). This is the most common way of 720C<incr_skip> to skip the erroneous part). This is the most common way of
746using the method. 721using the method.
747 722
748And finally, in list context, it will try to extract as many objects 723And finally, in list context, it will try to extract as many objects
749from the stream as it can find and return them, or the empty list 724from the stream as it can find and return them, or the empty list
750otherwise. For this to work, there must be no separators between the JSON 725otherwise. For this to work, there must be no separators between the JSON
… …
779C<incr_parse> died, in which case the input buffer and incremental parser 754C<incr_parse> died, in which case the input buffer and incremental parser
780state is left unchanged, to skip the text parsed so far and to reset the 755state is left unchanged, to skip the text parsed so far and to reset the
781parse state. 756parse state.
782 757
783The difference to C<incr_reset> is that only text until the parse error 758The difference to C<incr_reset> is that only text until the parse error
784occured is removed. 759occurred is removed.
785 760
786=item $json->incr_reset 761=item $json->incr_reset
787 762
788This completely resets the incremental parser, that is, after this call, 763This completely resets the incremental parser, that is, after this call,
789it will be as if the parser had never parsed anything. 764it will be as if the parser had never parsed anything.
… …
795=back 770=back
796 771
797=head2 LIMITATIONS 772=head2 LIMITATIONS
798 773
799All options that affect decoding are supported, except 774All options that affect decoding are supported, except
800C<allow_nonref>. The reason for this is that it cannot be made to 775C<allow_nonref>. The reason for this is that it cannot be made to work
801work sensibly: JSON objects and arrays are self-delimited, i.e. you can concatenate 776sensibly: JSON objects and arrays are self-delimited, i.e. you can
802them back to back and still decode them perfectly. This does not hold true 777concatenate them back to back and still decode them perfectly. This does
803for JSON numbers, however. 778not hold true for JSON numbers, however.
804 779
805For example, is the string C<1> a single JSON number, or is it simply the 780For example, is the string C<1> a single JSON number, or is it simply the
806start of C<12>? Or is C<12> a single JSON number, or the concatenation 781start of C<12>? Or is C<12> a single JSON number, or the concatenation
807of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS 782of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS
808takes the conservative route and disallows this case. 783takes the conservative route and disallows this case.
… …
987If the number consists of digits only, JSON::XS will try to represent 962If the number consists of digits only, JSON::XS will try to represent
988it as an integer value. If that fails, it will try to represent it as 963it as an integer value. If that fails, it will try to represent it as
989a numeric (floating point) value if that is possible without loss of 964a numeric (floating point) value if that is possible without loss of
990precision. Otherwise it will preserve the number as a string value (in 965precision. Otherwise it will preserve the number as a string value (in
991which case you lose roundtripping ability, as the JSON number will be 966which case you lose roundtripping ability, as the JSON number will be
992re-encoded toa JSON string). 967re-encoded to a JSON string).
993 968
994Numbers containing a fractional or exponential part will always be 969Numbers containing a fractional or exponential part will always be
995represented as numeric (floating point) values, possibly at a loss of 970represented as numeric (floating point) values, possibly at a loss of
996precision (in which case you might lose perfect roundtripping ability, but 971precision (in which case you might lose perfect roundtripping ability, but
997the JSON number will still be re-encoded as a JSON number). 972the JSON number will still be re-encoded as a JSON number).
998 973
999Note that precision is not accuracy - binary floating point values cannot 974Note that precision is not accuracy - binary floating point values cannot
1000represent most decimal fractions exactly, and when converting from and to 975represent most decimal fractions exactly, and when converting from and to
1001floating point, JSON::XS only guarantees precision up to but not including 976floating point, JSON::XS only guarantees precision up to but not including
1002the leats significant bit. 977the least significant bit.
1003 978
1004=item true, false 979=item true, false
1005 980
1006These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, 981These JSON atoms become C<Types::Serialiser::true> and
1007respectively. They are overloaded to act almost exactly like the numbers 982C<Types::Serialiser::false>, respectively. They are overloaded to act
1008C<1> and C<0>. You can check whether a scalar is a JSON boolean by using 983almost exactly like the numbers C<1> and C<0>. You can check whether
1009the C<JSON::XS::is_bool> function. 984a scalar is a JSON boolean by using the C<Types::Serialiser::is_bool>
985function (after C<use Types::Serialier>, of course).
1010 986
1011=item null 987=item null
1012 988
1013A JSON null atom becomes C<undef> in Perl. 989A JSON null atom becomes C<undef> in Perl.
990
991=item shell-style comments (C<< # I<text> >>)
992
993As a nonstandard extension to the JSON syntax that is enabled by the
994C<relaxed> setting, shell-style comments are allowed. They can start
995anywhere outside strings and go till the end of the line.
996
997=item tagged values (C<< (I<tag>)I<value> >>).
998
999Another nonstandard extension to the JSON syntax, enabled with the
1000C<allow_tags> setting, are tagged values. In this implementation, the
1001I<tag> must be a perl package/class name encoded as a JSON string, and the
1002I<value> must be a JSON array encoding optional constructor arguments.
1003
1004See "OBJECT SERIALISATION", below, for details.
1014 1005
1015=back 1006=back
1016 1007
1017 1008
1018=head2 PERL -> JSON 1009=head2 PERL -> JSON
… …
1023 1014
1024=over 4 1015=over 4
1025 1016
1026=item hash references 1017=item hash references
1027 1018
1028Perl hash references become JSON objects. As there is no inherent ordering 1019Perl hash references become JSON objects. As there is no inherent
1029in hash keys (or JSON objects), they will usually be encoded in a 1020ordering in hash keys (or JSON objects), they will usually be encoded
1030pseudo-random order that can change between runs of the same program but 1021in a pseudo-random order. JSON::XS can optionally sort the hash keys
1031stays generally the same within a single run of a program. JSON::XS can 1022(determined by the I<canonical> flag), so the same datastructure will
1032optionally sort the hash keys (determined by the I<canonical> flag), so 1023serialise to the same JSON text (given same settings and version of
1033the same datastructure will serialise to the same JSON text (given same 1024JSON::XS), but this incurs a runtime overhead and is only rarely useful,
1034settings and version of JSON::XS), but this incurs a runtime overhead 1025e.g. when you want to compare some JSON text against another for equality.
1035and is only rarely useful, e.g. when you want to compare some JSON text
1036against another for equality.
1037 1026
1038=item array references 1027=item array references
1039 1028
1040Perl array references become JSON arrays. 1029Perl array references become JSON arrays.
1041 1030
1042=item other references 1031=item other references
1043 1032
1044Other unblessed references are generally not allowed and will cause an 1033Other unblessed references are generally not allowed and will cause an
1045exception to be thrown, except for references to the integers C<0> and 1034exception to be thrown, except for references to the integers C<0> and
1046C<1>, which get turned into C<false> and C<true> atoms in JSON. You can 1035C<1>, which get turned into C<false> and C<true> atoms in JSON.
1047also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability.
1048 1036
1037Since C<JSON::XS> uses the boolean model from L<Types::Serialiser>, you
1038can also C<use Types::Serialiser> and then use C<Types::Serialiser::false>
1039and C<Types::Serialiser::true> to improve readability.
1040
1041 use Types::Serialiser;
1049 encode_json [\0, JSON::XS::true] # yields [false,true] 1042 encode_json [\0, Types::Serialiser::true] # yields [false,true]
1050 1043
1051=item JSON::XS::true, JSON::XS::false 1044=item Types::Serialiser::true, Types::Serialiser::false
1052 1045
1053These special values become JSON true and JSON false values, 1046These special values from the L<Types::Serialiser> module become JSON true
1054respectively. You can also use C<\1> and C<\0> directly if you want. 1047and JSON false values, respectively. You can also use C<\1> and C<\0>
1048directly if you want.
1055 1049
1056=item blessed objects 1050=item blessed objects
1057 1051
1058Blessed objects are not directly representable in JSON. See the 1052Blessed objects are not directly representable in JSON, but C<JSON::XS>
1059C<allow_blessed> and C<convert_blessed> methods on various options on 1053allows various ways of handling objects. See "OBJECT SERIALISATION",
1060how to deal with this: basically, you can choose between throwing an 1054below, for details.
1061exception, encoding the reference as if it weren't blessed, or provide
1062your own serialiser method.
1063 1055
1064=item simple scalars 1056=item simple scalars
1065 1057
1066Simple Perl scalars (any scalar that is not a reference) are the most 1058Simple Perl scalars (any scalar that is not a reference) are the most
1067difficult objects to encode: JSON::XS will encode undefined scalars as 1059difficult objects to encode: JSON::XS will encode undefined scalars as
… …
1104infinities or NaN's - these cannot be represented in JSON, and it is an 1096infinities or NaN's - these cannot be represented in JSON, and it is an
1105error to pass those in. 1097error to pass those in.
1106 1098
1107=back 1099=back
1108 1100
1101=head2 OBJECT SERIALISATION
1102
1103As JSON cannot directly represent Perl objects, you have to choose between
1104a pure JSON representation (without the ability to deserialise the object
1105automatically again), and a nonstandard extension to the JSON syntax,
1106tagged values.
1107
1108=head3 SERIALISATION
1109
1110What happens when C<JSON::XS> encounters a Perl object depends on the
1111C<allow_blessed>, C<convert_blessed> and C<allow_tags> settings, which are
1112used in this order:
1113
1114=over 4
1115
1116=item 1. C<allow_tags> is enabled and object has a C<FREEZE> method.
1117
1118In this case, C<JSON::XS> uses the L<Types::Serialiser> object
1119serialisation protocol to create a tagged JSON value, using a nonstandard
1120extension to the JSON syntax.
1121
1122This works by invoking the C<FREEZE> method on the object, with the first
1123argument being the object to serialise, and the second argument being the
1124constant string C<JSON> to distinguish it from other serialisers.
1125
1126The C<FREEZE> method can return any number of values (i.e. zero or
1127more). These values and the paclkage/classname of the object will then be
1128encoded as a tagged JSON value in the following format:
1129
1130 ("classname")[FREEZE return values...]
1131
1132For example, the hypothetical C<My::Object> C<FREEZE> method might use the
1133objects C<type> and C<id> members to encode the object:
1134
1135 sub My::Object::FREEZE {
1136 my ($self, $serialiser) = @_;
1137
1138 ($self->{type}, $self->{id})
1139 }
1140
1141=item 2. C<convert_blessed> is enabled and object has a C<TO_JSON> method.
1142
1143In this case, the C<TO_JSON> method of the object is invoked in scalar
1144context. It must return a single scalar that can be directly encoded into
1145JSON. This scalar replaces the object in the JSON text.
1146
1147For example, the following C<TO_JSON> method will convert all L<URI>
1148objects to JSON strings when serialised. The fatc that these values
1149originally were L<URI> objects is lost.
1150
1151 sub URI::TO_JSON {
1152 my ($uri) = @_;
1153 $uri->as_string
1154 }
1155
1156=item 3. C<allow_blessed> is enabled.
1157
1158The object will be serialised as a JSON null value.
1159
1160=item 4. none of the above
1161
1162If none of the settings are enabled or the respective methods are missing,
1163C<JSON::XS> throws an exception.
1164
1165=back
1166
1167=head3 DESERIALISATION
1168
1169For deserialisation there are only two cases to consider: either
1170nonstandard tagging was used, in which case C<allow_tags> decides,
1171or objects cannot be automatically be deserialised, in which
1172case you can use postprocessing or the C<filter_json_object> or
1173C<filter_json_single_key_object> callbacks to get some real objects our of
1174your JSON.
1175
1176This section only considers the tagged value case: I a tagged JSON object
1177is encountered during decoding and C<allow_tags> is disabled, a parse
1178error will result (as if tagged values were not part of the grammar).
1179
1180If C<allow_tags> is enabled, C<JSON::XS> will look up the C<THAW> method
1181of the package/classname used during serialisation. If there is no such
1182method, the decoding will fail with an error.
1183
1184Otherwise, the C<THAW> method is invoked with the classname as first
1185argument, the constant string C<JSON> as second argument, and all the
1186values from the JSON array (the values originally returned by the
1187C<FREEZE> method) as remaining arguments.
1188
1189The method must then return the object. While technically you can return
1190any Perl scalar, you might have to enable the C<enable_nonref> setting to
1191make that work in all cases, so better return an actual blessed reference.
1192
1193As an example, let's implement a C<THAW> function that regenerates the
1194C<My::Object> from the C<FREEZE> example earlier:
1195
1196 sub My::Object::THAW {
1197 my ($class, $serialiser, $type, $id) = @_;
1198
1199 $class->new (type => $type, id => $id)
1200 }
1201
1109 1202
1110=head1 ENCODING/CODESET FLAG NOTES 1203=head1 ENCODING/CODESET FLAG NOTES
1111 1204
1112The interested reader might have seen a number of flags that signify 1205The interested reader might have seen a number of flags that signify
1113encodings or codesets - C<utf8>, C<latin1> and C<ascii>. There seems to be 1206encodings or codesets - C<utf8>, C<latin1> and C<ascii>. There seems to be
… …
1137=item C<utf8> flag disabled 1230=item C<utf8> flag disabled
1138 1231
1139When C<utf8> is disabled (the default), then C<encode>/C<decode> generate 1232When C<utf8> is disabled (the default), then C<encode>/C<decode> generate
1140and expect Unicode strings, that is, characters with high ordinal Unicode 1233and expect Unicode strings, that is, characters with high ordinal Unicode
1141values (> 255) will be encoded as such characters, and likewise such 1234values (> 255) will be encoded as such characters, and likewise such
1142characters are decoded as-is, no canges to them will be done, except 1235characters are decoded as-is, no changes to them will be done, except
1143"(re-)interpreting" them as Unicode codepoints or Unicode characters, 1236"(re-)interpreting" them as Unicode codepoints or Unicode characters,
1144respectively (to Perl, these are the same thing in strings unless you do 1237respectively (to Perl, these are the same thing in strings unless you do
1145funny/weird/dumb stuff). 1238funny/weird/dumb stuff).
1146 1239
1147This is useful when you want to do the encoding yourself (e.g. when you 1240This is useful when you want to do the encoding yourself (e.g. when you
… …
1263output for these property strings, e.g.: 1356output for these property strings, e.g.:
1264 1357
1265 $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; 1358 $json =~ s/"__proto__"\s*:/"__proto__renamed":/g;
1266 1359
1267This works because C<__proto__> is not valid outside of strings, so every 1360This works because C<__proto__> is not valid outside of strings, so every
1268occurence of C<"__proto__"\s*:> must be a string used as property name. 1361occurrence of C<"__proto__"\s*:> must be a string used as property name.
1269 1362
1270If you know of other incompatibilities, please let me know. 1363If you know of other incompatibilities, please let me know.
1271 1364
1272 1365
1273=head2 JSON and YAML 1366=head2 JSON and YAML
… …
1319that difficult or long) and finally make YAML compatible to it, and 1412that difficult or long) and finally make YAML compatible to it, and
1320educating users about the changes, instead of spreading lies about the 1413educating users about the changes, instead of spreading lies about the
1321real compatibility for many I<years> and trying to silence people who 1414real compatibility for many I<years> and trying to silence people who
1322point out that it isn't true. 1415point out that it isn't true.
1323 1416
1324Addendum/2009: the YAML 1.2 spec is still incomaptible with JSON, even 1417Addendum/2009: the YAML 1.2 spec is still incompatible with JSON, even
1325though the incompatibilities have been documented (and are known to 1418though the incompatibilities have been documented (and are known to Brian)
1326Brian) for many years and the spec makes explicit claims that YAML is a 1419for many years and the spec makes explicit claims that YAML is a superset
1327superset of JSON. It would be so easy to fix, but apparently, bullying and 1420of JSON. It would be so easy to fix, but apparently, bullying people and
1328corrupting userdata is so much easier. 1421corrupting userdata is so much easier.
1329 1422
1330=back 1423=back
1331 1424
1332 1425
… …
1435are browser design bugs, but it is still you who will have to deal with 1528are browser design bugs, but it is still you who will have to deal with
1436it, as major browser developers care only for features, not about getting 1529it, as major browser developers care only for features, not about getting
1437security right). 1530security right).
1438 1531
1439 1532
1533=head1 INTEROPERABILITY WITH OTHER MODULES
1534
1535C<JSON::XS> uses the L<Types::Serialiser> module to provide boolean
1536constants. That means that the JSON true and false values will be
1537comaptible to true and false values of iother modules that do the same,
1538such as L<JSON::PP> and L<CBOR::XS>.
1539
1540
1440=head1 THREADS 1541=head1 THREADS
1441 1542
1442This module is I<not> guaranteed to be thread safe and there are no 1543This module is I<not> guaranteed to be thread safe and there are no
1443plans to change this until Perl gets thread support (as opposed to the 1544plans to change this until Perl gets thread support (as opposed to the
1444horribly slow so-called "threads" which are simply slow and bloated 1545horribly slow so-called "threads" which are simply slow and bloated
1445process simulations - use fork, it's I<much> faster, cheaper, better). 1546process simulations - use fork, it's I<much> faster, cheaper, better).
1446 1547
1447(It might actually work, but you have been warned). 1548(It might actually work, but you have been warned).
1448 1549
1449 1550
1551=head1 THE PERILS OF SETLOCALE
1552
1553Sometimes people avoid the Perl locale support and directly call the
1554system's setlocale function with C<LC_ALL>.
1555
1556This breaks both perl and modules such as JSON::XS, as stringification of
1557numbers no longer works correctly (e.g. C<$x = 0.1; print "$x"+1> might
1558print C<1>, and JSON::XS might output illegal JSON as JSON::XS relies on
1559perl to stringify numbers).
1560
1561The solution is simple: don't call C<setlocale>, or use it for only those
1562categories you need, such as C<LC_MESSAGES> or C<LC_CTYPE>.
1563
1564If you need C<LC_NUMERIC>, you should enable it only around the code that
1565actually needs it (avoiding stringification of numbers), and restore it
1566afterwards.
1567
1568
1450=head1 BUGS 1569=head1 BUGS
1451 1570
1452While the goal of this module is to be correct, that unfortunately does 1571While the goal of this module is to be correct, that unfortunately does
1453not mean it's bug-free, only that I think its design is bug-free. If you 1572not mean it's bug-free, only that I think its design is bug-free. If you
1454keep reporting bugs they will be fixed swiftly, though. 1573keep reporting bugs they will be fixed swiftly, though.
… …
1456Please refrain from using rt.cpan.org or any other bug reporting 1575Please refrain from using rt.cpan.org or any other bug reporting
1457service. I put the contact address into my modules for a reason. 1576service. I put the contact address into my modules for a reason.
1458 1577
1459=cut 1578=cut
1460 1579
1461our $true = do { bless \(my $dummy = 1), "JSON::XS::Boolean" }; 1580BEGIN {
1462our $false = do { bless \(my $dummy = 0), "JSON::XS::Boolean" }; 1581 *true = \$Types::Serialiser::true;
1582 *true = \&Types::Serialiser::true;
1583 *false = \$Types::Serialiser::false;
1584 *false = \&Types::Serialiser::false;
1585 *is_bool = \&Types::Serialiser::is_bool;
1463 1586
1464sub true() { $true } 1587 *JSON::XS::Boolean:: = *Types::Serialiser::Boolean::;
1465sub false() { $false }
1466
1467sub is_bool($) {
1468 UNIVERSAL::isa $_[0], "JSON::XS::Boolean"
1469# or UNIVERSAL::isa $_[0], "JSON::Literal"
1470} 1588}
1471 1589
1472XSLoader::load "JSON::XS", $VERSION; 1590XSLoader::load "JSON::XS", $VERSION;
1473
1474package JSON::XS::Boolean;
1475
1476use overload
1477 "0+" => sub { ${$_[0]} },
1478 "++" => sub { $_[0] = ${$_[0]} + 1 },
1479 "--" => sub { $_[0] = ${$_[0]} - 1 },
1480 fallback => 1;
1481
14821;
1483 1591
1484=head1 SEE ALSO 1592=head1 SEE ALSO
1485 1593
1486The F<json_xs> command line utility for quick experiments. 1594The F<json_xs> command line utility for quick experiments.
1487 1595
… …
1490 Marc Lehmann <schmorp@schmorp.de> 1598 Marc Lehmann <schmorp@schmorp.de>
1491 http://home.schmorp.de/ 1599 http://home.schmorp.de/
1492 1600
1493=cut 1601=cut
1494 1602
16031
1604

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines