JSON serialising/deserialising, done correctly and fast
This module converts Perl data structures to JSON and vice versa. Its
primary goal is to be *correct* and its secondary goal is to be *fast*.
To reach the latter goal it was written in C.
Beginning with version 2.0 of the JSON module, when both JSON and
JSON::XS are installed, then JSON will fall back on JSON::XS (this can
be overridden) with no overhead due to emulation (by inheriting
constructor and methods). If JSON::XS is not available, it will fall
back to the compatible JSON::PP module as backend, so using JSON instead
of JSON::XS gives you a portable JSON API that can be fast when you need
and doesn`t require a C compiler when that is a problem.
As this is the n-th-something JSON module on CPAN, what was the reason
to write yet another JSON module? While it seems there are many JSON
modules, none of them correctly handle all corner cases, and in most
cases their maintainers are unresponsive, gone missing, or not listening
to bug reports for other reasons.
Author:
-------
Marc Lehmann
- Developed at devel:languages:perl
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:zSystems/perl-JSON-XS && cd $_ - Create Badge
Source Files
| Filename | Size | Changed |
|---|---|---|
| JSON-XS-3.01.tar.gz | 0000078245 76.4 KB | |
| perl-JSON-XS.changes | 0000004827 4.71 KB | |
| perl-JSON-XS.spec | 0000002881 2.81 KB |
Revision 16 (latest revision is 24)
Stephan Kulow (coolo)
accepted
request 208246
from
Stephan Kulow (coolo)
(revision 16)
- updated to 3.01
- backport to perls < 5.18 (reported by Paul Howarth).
- implemented an object tagging extension (using the
Types::Serialiser serialisation protocol).
- reworked the documentation regarding object serialisation,
add a new OBJECT SERIALISATION section that explains the
whole process.
- new setting: allow_tags.
- switch to Types::Serialiser booleans.
- remove to_json/from_json.
- other minor improvements to the documentation.
Comments 0