--- JSON-XS/XS.pm	2008/05/27 05:31:39	1.106
+++ JSON-XS/XS.pm	2008/07/21 02:45:17	1.111
@@ -51,8 +51,6 @@
 their maintainers are unresponsive, gone missing, or not listening to bug
 reports for other reasons.
 
-See COMPARISON, below, for a comparison to some other JSON modules.
-
 See MAPPING, below, on how JSON::XS maps perl values to JSON values and
 vice versa.
 
@@ -103,9 +101,10 @@
 
 package JSON::XS;
 
+no warnings;
 use strict;
 
-our $VERSION = '2.2';
+our $VERSION = '2.2222';
 our @ISA = qw(Exporter);
 
 our @EXPORT = qw(encode_json decode_json to_json from_json);
@@ -708,12 +707,20 @@
 Perl data structure in memory at one time, it does allow you to parse a
 JSON stream incrementally. It does so by accumulating text until it has
 a full JSON object, which it then can decode. This process is similar to
-using C<decode_prefix> to see if a full JSON object is available, but is
-much more efficient (JSON::XS will only attempt to parse the JSON text
-once it is sure it has enough text to get a decisive result, using a very
-simple but truly incremental parser).
+using C<decode_prefix> to see if a full JSON object is available, but
+is much more efficient (and can be implemented with a minimum of method
+calls).
+
+JSON::XS will only attempt to parse the JSON text once it is sure it
+has enough text to get a decisive result, using a very simple but
+truly incremental parser. This means that it sometimes won't stop as
+early as the full parser, for example, it doesn't detect parenthese
+mismatches. The only thing it guarantees is that it starts decoding as
+soon as a syntactically valid JSON text has been seen. This means you need
+to set resource limits (e.g. C<max_size>) to ensure the parser will stop
+parsing in the presence if syntax errors.
 
-The following two methods deal with this.
+The following methods implement this incremental parser.
 
 =over 4