--- JSON-XS/XS.pm	2007/03/29 01:27:36	1.24
+++ JSON-XS/XS.pm	2007/04/12 07:25:29	1.32
@@ -88,7 +88,7 @@
 use strict;
 
 BEGIN {
-   our $VERSION = '0.8';
+   our $VERSION = '1.12';
    our @ISA = qw(Exporter);
 
    our @EXPORT = qw(to_json from_json objToJson jsonToObj);
@@ -156,7 +156,9 @@
 generate characters outside the code range C<0..127> (which is ASCII). Any
 unicode characters outside that range will be escaped using either a
 single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence,
-as per RFC4627.
+as per RFC4627. The resulting encoded JSON text can be treated as a native
+unicode string, an ascii-encoded, latin1-encoded or UTF-8 encoded string,
+or any other superset of ASCII.
 
 If C<$enable> is false, then the C<encode> method will not escape Unicode
 characters unless required by the JSON syntax. This results in a faster
@@ -311,7 +313,7 @@
 
 =item $json = $json->max_depth ([$maximum_nesting_depth])
 
-Sets the maximum nesting level (default C<8192>) accepted while encoding
+Sets the maximum nesting level (default C<512>) accepted while encoding
 or decoding. If the JSON text or Perl data structure has an equal or
 higher nesting level then this limit, then the encoder and decoder will
 stop and croak at that point.
@@ -412,17 +414,28 @@
 =item hash references
 
 Perl hash references become JSON objects. As there is no inherent ordering
-in hash keys, they will usually be encoded in a pseudo-random order that
-can change between runs of the same program but stays generally the same
-within a single run of a program. JSON::XS can optionally sort the hash
-keys (determined by the I<canonical> flag), so the same datastructure
-will serialise to the same JSON text (given same settings and version of
-JSON::XS), but this incurs a runtime overhead.
+in hash keys (or JSON objects), they will usually be encoded in a
+pseudo-random order that can change between runs of the same program but
+stays generally the same within a single run of a program. JSON::XS can
+optionally sort the hash keys (determined by the I<canonical> flag), so
+the same datastructure will serialise to the same JSON text (given same
+settings and version of JSON::XS), but this incurs a runtime overhead
+and is only rarely useful, e.g. when you want to compare some JSON text
+against another for equality.
 
 =item array references
 
 Perl array references become JSON arrays.
 
+=item other references
+
+Other unblessed references are generally not allowed and will cause an
+exception to be thrown, except for references to the integers C<0> and
+C<1>, which get turned into C<false> and C<true> atoms in JSON. You can
+also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability.
+
+   to_json [\0,JSON::XS::true]      # yields [false,true]
+
 =item blessed objects
 
 Blessed objects are not allowed. JSON::XS currently tries to encode their
@@ -464,10 +477,6 @@
 You can not currently output JSON booleans or force the type in other,
 less obscure, ways. Tell me if you need this capability.
 
-=item circular data structures
-
-Those will be encoded until memory or stackspace runs out.
-
 =back
 
 
@@ -627,14 +636,15 @@
 
 Third, JSON::XS recurses using the C stack when decoding objects and
 arrays. The C stack is a limited resource: for instance, on my amd64
-machine with 8MB of stack size I can decode around 180k nested arrays
-but only 14k nested JSON objects. If that is exceeded, the program
-crashes. Thats why the default nesting limit is set to 8192. If your
-process has a smaller stack, you should adjust this setting accordingly
-with the C<max_depth> method.
+machine with 8MB of stack size I can decode around 180k nested arrays but
+only 14k nested JSON objects (due to perl itself recursing deeply on croak
+to free the temporary). If that is exceeded, the program crashes. to be
+conservative, the default nesting limit is set to 512. If your process
+has a smaller stack, you should adjust this setting accordingly with the
+C<max_depth> method.
 
 And last but least, something else could bomb you that I forgot to think
-of. In that case, you get to keep the pieces. I am alway sopen for hints,
+of. In that case, you get to keep the pieces. I am always open for hints,
 though...
 
 
@@ -647,6 +657,9 @@
 
 =cut
 
+sub true()  { \1 }
+sub false() { \0 }
+
 1;
 
 =head1 AUTHOR