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.121 by root, Mon Jul 13 22:13:17 2009 UTC vs.
Revision 1.126 by root, Wed Jan 6 08:02:18 2010 UTC

… …
101 101
102package JSON::XS; 102package JSON::XS;
103 103
104use common::sense; 104use common::sense;
105 105
106our $VERSION = '2.24'; 106our $VERSION = '2.27';
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($) {
… …
440the same JSON text (given the same overall settings). If it is disabled, 440the 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, 441the same hash might be encoded differently even if contains the same data,
442as key-value pairs have no inherent ordering in Perl. 442as key-value pairs have no inherent ordering in Perl.
443 443
444This setting has no effect when decoding JSON texts. 444This setting has no effect when decoding JSON texts.
445
446This setting has currently no effect on tied hashes.
445 447
446=item $json = $json->allow_nonref ([$enable]) 448=item $json = $json->allow_nonref ([$enable])
447 449
448=item $enabled = $json->get_allow_nonref 450=item $enabled = $json->get_allow_nonref
449 451
… …
1266 my $yaml = $to_yaml->encode ($ref) . "\n"; 1268 my $yaml = $to_yaml->encode ($ref) . "\n";
1267 1269
1268This will I<usually> generate JSON texts that also parse as valid 1270This will I<usually> generate JSON texts that also parse as valid
1269YAML. Please note that YAML has hardcoded limits on (simple) object key 1271YAML. Please note that YAML has hardcoded limits on (simple) object key
1270lengths that JSON doesn't have and also has different and incompatible 1272lengths that JSON doesn't have and also has different and incompatible
1271unicode handling, so you should make sure that your hash keys are 1273unicode character escape syntax, so you should make sure that your hash
1272noticeably shorter than the 1024 "stream characters" YAML allows and that 1274keys are noticeably shorter than the 1024 "stream characters" YAML allows
1273you do not have characters with codepoint values outside the Unicode BMP 1275and that you do not have characters with codepoint values outside the
1274(basic multilingual page). YAML also does not allow C<\/> sequences in 1276Unicode BMP (basic multilingual page). YAML also does not allow C<\/>
1275strings (which JSON::XS does not I<currently> generate, but other JSON 1277sequences in strings (which JSON::XS does not I<currently> generate, but
1276generators might). 1278other JSON generators might).
1277 1279
1278There might be other incompatibilities that I am not aware of (or the YAML 1280There might be other incompatibilities that I am not aware of (or the YAML
1279specification has been changed yet again - it does so quite often). In 1281specification has been changed yet again - it does so quite often). In
1280general you should not try to generate YAML with a JSON generator or vice 1282general you should not try to generate YAML with a JSON generator or vice
1281versa, or try to parse JSON with a YAML parser or vice versa: chances are 1283versa, or try to parse JSON with a YAML parser or vice versa: chances are
… …
1299proponents, I would kindly suggest reading the JSON spec (which is not 1301proponents, I would kindly suggest reading the JSON spec (which is not
1300that difficult or long) and finally make YAML compatible to it, and 1302that difficult or long) and finally make YAML compatible to it, and
1301educating users about the changes, instead of spreading lies about the 1303educating users about the changes, instead of spreading lies about the
1302real compatibility for many I<years> and trying to silence people who 1304real compatibility for many I<years> and trying to silence people who
1303point out that it isn't true. 1305point out that it isn't true.
1306
1307Addendum/2009: the YAML 1.2 spec is still incomaptible with JSON, even
1308though the incompatibilities have been documented (and are known to
1309Brian) for many years and the spec makes explicit claims that YAML is a
1310superset of JSON. It would be so easy to fix, but apparently, bullying and
1311corrupting userdata is so much easier.
1304 1312
1305=back 1313=back
1306 1314
1307 1315
1308=head2 SPEED 1316=head2 SPEED

Diff Legend

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