--- JSON-XS/README	2009/02/19 01:13:46	1.29
+++ JSON-XS/README	2009/10/10 01:48:50	1.32
@@ -22,8 +22,8 @@
      # Note that JSON version 2.0 and above will automatically use JSON::XS
      # if available, at virtually no speed overhead either, so you should
      # be able to just:
-     
- use JSON;
+ 
+     use JSON;
 
      # and do the same things, except that you have a pure-perl fallback now.
 
@@ -380,6 +380,8 @@
 
         This setting has no effect when decoding JSON texts.
 
+        This setting has currently no effect on tied hashes.
+
     $json = $json->allow_nonref ([$enable])
     $enabled = $json->get_allow_nonref
         If $enable is true (or missing), then the "encode" method can
@@ -1153,10 +1155,10 @@
     This will *usually* generate JSON texts that also parse as valid YAML.
     Please note that YAML has hardcoded limits on (simple) object key
     lengths that JSON doesn't have and also has different and incompatible
-    unicode handling, so you should make sure that your hash keys are
-    noticeably shorter than the 1024 "stream characters" YAML allows and
-    that you do not have characters with codepoint values outside the
-    Unicode BMP (basic multilingual page). YAML also does not allow "\/"
+    unicode character escape syntax, so you should make sure that your hash
+    keys are noticeably shorter than the 1024 "stream characters" YAML
+    allows and that you do not have characters with codepoint values outside
+    the Unicode BMP (basic multilingual page). YAML also does not allow "\/"
     sequences in strings (which JSON::XS does not *currently* generate, but
     other JSON generators might).
 
@@ -1183,6 +1185,12 @@
         spreading lies about the real compatibility for many *years* and
         trying to silence people who point out that it isn't true.
 
+        Addendum/2009: the YAML 1.2 spec is still incomaptible with JSON,
+        even though the incompatibilities have been documented (and are
+        known to Brian) for many years and the spec makes explicit claims
+        that YAML is a superset of JSON. It would be so easy to fix, but
+        apparently, bullying and corrupting userdata is so much easier.
+
   SPEED
     It seems that JSON::XS is surprisingly fast, as shown in the following
     tables. They have been generated with the help of the "eg/bench" program