[ViewVC] Diff of: cvs/JSON-XS/XS.pm

Comparing JSON-XS/XS.pm (file contents):
Revision 1.148 by root, Tue Oct 29 00:19:45 2013 UTC vs.
Revision 1.150 by root, Tue Oct 29 00:48:07 2013 UTC

 C<allow_blessed>, C<convert_blessed> and C<allow_tags> settings, which are
 used in this order:
 =over 4
-=item 1. C<allow_tags> is enabled and object has a C<FREEZE> method.
+=item 1. C<allow_tags> is enabled and the object has a C<FREEZE> method.
 In this case, C<JSON::XS> uses the L<Types::Serialiser> object
 serialisation protocol to create a tagged JSON value, using a nonstandard
 extension to the JSON syntax.
 more). These values and the paclkage/classname of the object will then be
 encoded as a tagged JSON value in the following format:
    ("classname")[FREEZE return values...]
+e.g.:
+   ("URI")["http://www.google.com/"]
+   ("MyDate")[2013,10,29]
+   ("ImageData::JPEG")["Z3...VlCg=="]
 For example, the hypothetical C<My::Object> C<FREEZE> method might use the
 objects C<type> and C<id> members to encode the object:
    sub My::Object::FREEZE {
       my ($self, $serialiser) = @_;
       ($self->{type}, $self->{id})
    }
-=item 2. C<convert_blessed> is enabled and object has a C<TO_JSON> method.
+=item 2. C<convert_blessed> is enabled and the object has a C<TO_JSON> method.
 In this case, the C<TO_JSON> method of the object is invoked in scalar
 context. It must return a single scalar that can be directly encoded into
 JSON. This scalar replaces the object in the JSON text.

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