Group :: Desenvolvimento/Perl
RPM: perl-JSON-XS
Principal Changelog Spec Patches Sources Download Gear Bugs e FR Repocop
A versão atual: 2.1-alt1
Data da compilação: 13 abril 2008, 14:45 ( 838.4 weeks ago )
Tamanho:: 60.85 Kb
Home page: http://search.cpan.org/dist/JSON-XS/
Licença: Artistic
Sumário: JSON serialising/deserialising, done correctly and fast
Descrição:
Lista dos contribuidores Lista dos rpms provida por esta srpm:
ACL:
Data da compilação: 13 abril 2008, 14:45 ( 838.4 weeks ago )
Tamanho:: 60.85 Kb
Home page: http://search.cpan.org/dist/JSON-XS/
Licença: Artistic
Sumário: JSON serialising/deserialising, done correctly and fast
Descrição:
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
overriden) with no overhead due to emulation (by inheritign 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.
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.
Mantenedor currente: Michael Bochkaryov 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
overriden) with no overhead due to emulation (by inheritign 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.
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.
Lista dos contribuidores Lista dos rpms provida por esta srpm:
- perl-JSON-XS