Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: libjson-xs
Source: <url://example.com>
#
# Please double check copyright with the licensecheck(1) command.

Files:     Changes
           MANIFEST
           META.json
           META.yml
           Makefile.PL
           XS.xs
           XS/Boolean.pm
           eg/bench
           t/00_load.t
           t/01_utf8.t
           t/02_error.t
           t/03_types.t
           t/04_dwiw_encode.t
           t/05_dwiw_decode.t
           t/06_pc_pretty.t
           t/07_pc_esc.t
           t/08_pc_base.t
           t/09_pc_extra_number.t
           t/10_pc_keysort.t
           t/11_pc_expo.t
           t/12_blessed.t
           t/13_limit.t
           t/14_latin1.t
           t/15_prefix.t
           t/16_tied.t
           t/17_relaxed.t
           t/18_json_checker.t
           t/19_incr.t
           t/20_faihu.t
           t/21_evans.t
           t/22_comment_at_eof.t
           t/52_object.t
           t/99_binary.t
           typemap
Copyright: __NO_COPYRIGHT_NOR_LICENSE__
License:   __NO_COPYRIGHT_NOR_LICENSE__

Files:     README
Copyright: __NO_COPYRIGHT__ in: README
License:   __UNKNOWN__
 personally bitten by this "JSON is YAML" lie, I refused and said I
 will continue to educate people about these issues, so others do not
 run into the same problem again and again. After this, Brian called
 me a (quote)*complete and worthless idiot*(unquote).
 .
 In my opinion, instead of pressuring and insulting people who
 actually clarify issues with YAML and the wrong statements of some
 of its proponents, I would kindly suggest reading the JSON spec
 (which is not that difficult or long) and finally make YAML
 compatible to it, and educating users about the changes, instead of
 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 incompatible 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 people 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
 in the JSON::XS distribution, to make it easy to compare on your own
 system.
 .
 First comes a comparison between various modules using a very short
 single-line JSON string (also available at
 <http://dist.schmorp.de/misc/json/short.json>).
 .
 {"method": "handleMessage", "params": ["user1",
 "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7,
 1,  0]}
 .
 It shows the number of encodes/decodes per second (JSON::XS uses the
 functional interface, while JSON::XS/2 uses the OO interface with
 pretty-printing and hashkey sorting enabled, JSON::XS/3 enables shrink.
 JSON::DWIW/DS uses the deserialise function, while JSON::DWIW::FJ uses

Files:     XS.pm
Copyright: __NO_COPYRIGHT__ in: XS.pm
License:   __UNKNOWN__
 bitten by this "JSON is YAML" lie, I refused and said I will continue to
 educate people about these issues, so others do not run into the same
 problem again and again. After this, Brian called me a (quote)I<complete
 and worthless idiot>(unquote).
 .
 In my opinion, instead of pressuring and insulting people who actually
 clarify issues with YAML and the wrong statements of some of its
 proponents, I would kindly suggest reading the JSON spec (which is not
 that difficult or long) and finally make YAML compatible to it, and
 educating users about the changes, instead of spreading lies about the
 real compatibility for many I<years> and trying to silence people who
 point out that it isn't true.
 .
 Addendum/2009: the YAML 1.2 spec is still incompatible 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 people and
 corrupting userdata is so much easier.

Files:     bin/json_xs
Copyright: 2008 Marc Lehmann <json@schmorp.de>
License:   __NO_LICENSE__

#----------------------------------------------------------------------------
# Files marked as NO_LICENSE_TEXT_FOUND may be covered by the following
# license/copyright files.

#----------------------------------------------------------------------------
# License file: COPYING
 This module is licensed under the same terms as perl itself.
 .
