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.131 by root, Thu Mar 11 19:31:37 2010 UTC vs.
Revision 1.137 by root, Thu Aug 11 17:06:53 2011 UTC

101 101
102package JSON::XS; 102package JSON::XS;
103 103
104use common::sense; 104use common::sense;
105 105
106our $VERSION = '2.28'; 106our $VERSION = '2.32';
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 to_json from_json);
110 110
111sub to_json($) { 111sub to_json($) {
713calls). 713calls).
714 714
715JSON::XS will only attempt to parse the JSON text once it is sure it 715JSON::XS will only attempt to parse the JSON text once it is sure it
716has enough text to get a decisive result, using a very simple but 716has enough text to get a decisive result, using a very simple but
717truly incremental parser. This means that it sometimes won't stop as 717truly incremental parser. This means that it sometimes won't stop as
718early as the full parser, for example, it doesn't detect parenthese 718early as the full parser, for example, it doesn't detect mismatched
719mismatches. The only thing it guarantees is that it starts decoding as 719parentheses. The only thing it guarantees is that it starts decoding as
720soon as a syntactically valid JSON text has been seen. This means you need 720soon as a syntactically valid JSON text has been seen. This means you need
721to set resource limits (e.g. C<max_size>) to ensure the parser will stop 721to set resource limits (e.g. C<max_size>) to ensure the parser will stop
722parsing in the presence if syntax errors. 722parsing in the presence if syntax errors.
723 723
724The following methods implement this incremental parser. 724The following methods implement this incremental parser.
1255well - using C<eval> naively simply I<will> cause problems. 1255well - using C<eval> naively simply I<will> cause problems.
1256 1256
1257Another problem is that some javascript implementations reserve 1257Another problem is that some javascript implementations reserve
1258some property names for their own purposes (which probably makes 1258some property names for their own purposes (which probably makes
1259them non-ECMAscript-compliant). For example, Iceweasel reserves the 1259them non-ECMAscript-compliant). For example, Iceweasel reserves the
1260C<__proto__> property name for it's own purposes. 1260C<__proto__> property name for its own purposes.
1261 1261
1262If that is a problem, you could parse try to filter the resulting JSON 1262If that is a problem, you could parse try to filter the resulting JSON
1263output for these property strings, e.g.: 1263output for these property strings, e.g.:
1264 1264
1265 $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; 1265 $json =~ s/"__proto__"\s*:/"__proto__renamed":/g;
1319that difficult or long) and finally make YAML compatible to it, and 1319that difficult or long) and finally make YAML compatible to it, and
1320educating users about the changes, instead of spreading lies about the 1320educating users about the changes, instead of spreading lies about the
1321real compatibility for many I<years> and trying to silence people who 1321real compatibility for many I<years> and trying to silence people who
1322point out that it isn't true. 1322point out that it isn't true.
1323 1323
1324Addendum/2009: the YAML 1.2 spec is still incomaptible with JSON, even 1324Addendum/2009: the YAML 1.2 spec is still incompatible with JSON, even
1325though the incompatibilities have been documented (and are known to 1325though the incompatibilities have been documented (and are known to Brian)
1326Brian) for many years and the spec makes explicit claims that YAML is a 1326for 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 1327of JSON. It would be so easy to fix, but apparently, bullying people and
1328corrupting userdata is so much easier. 1328corrupting userdata is so much easier.
1329 1329
1330=back 1330=back
1331 1331
1332 1332

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines