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

Comparing JSON-XS/XS.pm (file contents):
Revision 1.26 by root, Sat Mar 31 14:20:06 2007 UTC vs.
Revision 1.83 by root, Sun Jan 20 19:19:07 2008 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	JSON::XS - JSON serialising/deserialising, done correctly and fast	3	JSON::XS - JSON serialising/deserialising, done correctly and fast
		4
		5	JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ
		6	(http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html)
4		7
5	=head1 SYNOPSIS	8	=head1 SYNOPSIS
6		9
7	use JSON::XS;	10	use JSON::XS;
8		11
9	# exported functions, they croak on error	12	# exported functions, they croak on error
10	# and expect/generate UTF-8	13	# and expect/generate UTF-8
11		14
12	$utf8_encoded_json_text = to_json $perl_hash_or_arrayref;	15	$utf8_encoded_json_text = encode_json $perl_hash_or_arrayref;
13	$perl_hash_or_arrayref = from_json $utf8_encoded_json_text;	16	$perl_hash_or_arrayref = decode_json $utf8_encoded_json_text;
14
15	# objToJson and jsonToObj aliases to to_json and from_json
16	# are exported for compatibility to the JSON module,
17	# but should not be used in new code.
18		17
19	# OO-interface	18	# OO-interface
20		19
21	$coder = JSON::XS->new->ascii->pretty->allow_nonref;	20	$coder = JSON::XS->new->ascii->pretty->allow_nonref;
22	$pretty_printed_unencoded = $coder->encode ($perl_scalar);	21	$pretty_printed_unencoded = $coder->encode ($perl_scalar);
23	$perl_scalar = $coder->decode ($unicode_json_text);	22	$perl_scalar = $coder->decode ($unicode_json_text);
24		23
		24	# Note that JSON version 2.0 and above will automatically use JSON::XS
		25	# if available, at virtually no speed overhead either, so you should
		26	# be able to just:
		27
		28	use JSON;
		29
		30	# and do the same things, except that you have a pure-perl fallback now.
		31
25	=head1 DESCRIPTION	32	=head1 DESCRIPTION
26		33
27	This module converts Perl data structures to JSON and vice versa. Its	34	This module converts Perl data structures to JSON and vice versa. Its
28	primary goal is to be I<correct> and its secondary goal is to be	35	primary goal is to be I<correct> and its secondary goal is to be
29	I<fast>. To reach the latter goal it was written in C.	36	I<fast>. To reach the latter goal it was written in C.
		37
		38	Beginning with version 2.0 of the JSON module, when both JSON and
		39	JSON::XS are installed, then JSON will fall back on JSON::XS (this can be
		40	overriden) with no overhead due to emulation (by inheritign constructor
		41	and methods). If JSON::XS is not available, it will fall back to the
		42	compatible JSON::PP module as backend, so using JSON instead of JSON::XS
		43	gives you a portable JSON API that can be fast when you need and doesn't
		44	require a C compiler when that is a problem.
30		45
31	As this is the n-th-something JSON module on CPAN, what was the reason	46	As this is the n-th-something JSON module on CPAN, what was the reason
32	to write yet another JSON module? While it seems there are many JSON	47	to write yet another JSON module? While it seems there are many JSON
33	modules, none of them correctly handle all corner cases, and in most cases	48	modules, none of them correctly handle all corner cases, and in most cases
34	their maintainers are unresponsive, gone missing, or not listening to bug	49	their maintainers are unresponsive, gone missing, or not listening to bug
41		56
42	=head2 FEATURES	57	=head2 FEATURES
43		58
44	=over 4	59	=over 4
45		60
46	=item * correct unicode handling	61	=item * correct Unicode handling
47		62
48	This module knows how to handle Unicode, and even documents how and when	63	This module knows how to handle Unicode, and even documents how and when
49	it does so.	64	it does so.
50		65
51	=item * round-trip integrity	66	=item * round-trip integrity
…		…
71	This module has both a simple functional interface as well as an OO	86	This module has both a simple functional interface as well as an OO
72	interface.	87	interface.
73		88
74	=item * reasonably versatile output formats	89	=item * reasonably versatile output formats
75		90
76	You can choose between the most compact guarenteed single-line format	91	You can choose between the most compact guaranteed single-line format
77	possible (nice for simple line-based protocols), a pure-ascii format	92	possible (nice for simple line-based protocols), a pure-ascii format
78	(for when your transport is not 8-bit clean, still supports the whole	93	(for when your transport is not 8-bit clean, still supports the whole
79	unicode range), or a pretty-printed format (for when you want to read that	94	Unicode range), or a pretty-printed format (for when you want to read that
80	stuff). Or you can combine those features in whatever way you like.	95	stuff). Or you can combine those features in whatever way you like.
81		96
82	=back	97	=back
83		98
84	=cut	99	=cut
85		100
86	package JSON::XS;	101	package JSON::XS;
87		102
88	use strict;	103	use strict;
89		104
90	BEGIN {
91	our $VERSION = '1.01';	105	our $VERSION = '2.01';
92	our @ISA = qw(Exporter);	106	our @ISA = qw(Exporter);
93		107
94	our @EXPORT = qw(to_json from_json objToJson jsonToObj);	108	our @EXPORT = qw(encode_json decode_json to_json from_json);
95	require Exporter;
96		109
		110	sub to_json($) {
97	require XSLoader;	111	require Carp;
98	XSLoader::load JSON::XS::, $VERSION;	112	Carp::croak ("JSON::XS::to_json has been renamed to encode_json, either downgrade to pre-2.0 versions of JSON::XS or rename the call");
99	}	113	}
100		114
		115	sub from_json($) {
		116	require Carp;
		117	Carp::croak ("JSON::XS::from_json has been renamed to decode_json, either downgrade to pre-2.0 versions of JSON::XS or rename the call");
		118	}
		119
		120	use Exporter;
		121	use XSLoader;
		122
101	=head1 FUNCTIONAL INTERFACE	123	=head1 FUNCTIONAL INTERFACE
102		124
103	The following convinience methods are provided by this module. They are	125	The following convenience methods are provided by this module. They are
104	exported by default:	126	exported by default:
105		127
106	=over 4	128	=over 4
107		129
108	=item $json_text = to_json $perl_scalar	130	=item $json_text = encode_json $perl_scalar
109		131
110	Converts the given Perl data structure (a simple scalar or a reference to	132	Converts the given Perl data structure to a UTF-8 encoded, binary string
111	a hash or array) to a UTF-8 encoded, binary string (that is, the string contains	133	(that is, the string contains octets only). Croaks on error.
112	octets only). Croaks on error.
113		134
114	This function call is functionally identical to:	135	This function call is functionally identical to:
115		136
116	$json_text = JSON::XS->new->utf8->encode ($perl_scalar)	137	$json_text = JSON::XS->new->utf8->encode ($perl_scalar)
117		138
118	except being faster.	139	except being faster.
119		140
120	=item $perl_scalar = from_json $json_text	141	=item $perl_scalar = decode_json $json_text
121		142
122	The opposite of C<to_json>: expects an UTF-8 (binary) string and tries to	143	The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries
123	parse that as an UTF-8 encoded JSON text, returning the resulting simple	144	to parse that as an UTF-8 encoded JSON text, returning the resulting
124	scalar or reference. Croaks on error.	145	reference. Croaks on error.
125		146
126	This function call is functionally identical to:	147	This function call is functionally identical to:
127		148
128	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)	149	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)
129		150
130	except being faster.	151	except being faster.
131		152
		153	=item $is_boolean = JSON::XS::is_bool $scalar
		154
		155	Returns true if the passed scalar represents either JSON::XS::true or
		156	JSON::XS::false, two constants that act like C<1> and C<0>, respectively
		157	and are used to represent JSON C<true> and C<false> values in Perl.
		158
		159	See MAPPING, below, for more information on how JSON values are mapped to
		160	Perl.
		161
132	=back	162	=back
		163
		164
		165	=head1 A FEW NOTES ON UNICODE AND PERL
		166
		167	Since this often leads to confusion, here are a few very clear words on
		168	how Unicode works in Perl, modulo bugs.
		169
		170	=over 4
		171
		172	=item 1. Perl strings can store characters with ordinal values > 255.
		173
		174	This enables you to store Unicode characters as single characters in a
		175	Perl string - very natural.
		176
		177	=item 2. Perl does I<not> associate an encoding with your strings.
		178
		179	Unless you force it to, e.g. when matching it against a regex, or printing
		180	the scalar to a file, in which case Perl either interprets your string as
		181	locale-encoded text, octets/binary, or as Unicode, depending on various
		182	settings. In no case is an encoding stored together with your data, it is
		183	I<use> that decides encoding, not any magical metadata.
		184
		185	=item 3. The internal utf-8 flag has no meaning with regards to the
		186	encoding of your string.
		187
		188	Just ignore that flag unless you debug a Perl bug, a module written in
		189	XS or want to dive into the internals of perl. Otherwise it will only
		190	confuse you, as, despite the name, it says nothing about how your string
		191	is encoded. You can have Unicode strings with that flag set, with that
		192	flag clear, and you can have binary data with that flag set and that flag
		193	clear. Other possibilities exist, too.
		194
		195	If you didn't know about that flag, just the better, pretend it doesn't
		196	exist.
		197
		198	=item 4. A "Unicode String" is simply a string where each character can be
		199	validly interpreted as a Unicode codepoint.
		200
		201	If you have UTF-8 encoded data, it is no longer a Unicode string, but a
		202	Unicode string encoded in UTF-8, giving you a binary string.
		203
		204	=item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string.
		205
		206	It's a fact. Learn to live with it.
		207
		208	=back
		209
		210	I hope this helps :)
133		211
134		212
135	=head1 OBJECT-ORIENTED INTERFACE	213	=head1 OBJECT-ORIENTED INTERFACE
136		214
137	The object oriented interface lets you configure your own encoding or	215	The object oriented interface lets you configure your own encoding or
…		…
150	my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]})	228	my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]})
151	=> {"a": [1, 2]}	229	=> {"a": [1, 2]}
152		230
153	=item $json = $json->ascii ([$enable])	231	=item $json = $json->ascii ([$enable])
154		232
		233	=item $enabled = $json->get_ascii
		234
155	If C<$enable> is true (or missing), then the C<encode> method will not	235	If C<$enable> is true (or missing), then the C<encode> method will not
156	generate characters outside the code range C<0..127> (which is ASCII). Any	236	generate characters outside the code range C<0..127> (which is ASCII). Any
157	unicode characters outside that range will be escaped using either a	237	Unicode characters outside that range will be escaped using either a
158	single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence,	238	single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence,
159	as per RFC4627.	239	as per RFC4627. The resulting encoded JSON text can be treated as a native
		240	Unicode string, an ascii-encoded, latin1-encoded or UTF-8 encoded string,
		241	or any other superset of ASCII.
160		242
161	If C<$enable> is false, then the C<encode> method will not escape Unicode	243	If C<$enable> is false, then the C<encode> method will not escape Unicode
162	characters unless required by the JSON syntax. This results in a faster	244	characters unless required by the JSON syntax or other flags. This results
163	and more compact format.	245	in a faster and more compact format.
		246
		247	The main use for this flag is to produce JSON texts that can be
		248	transmitted over a 7-bit channel, as the encoded JSON texts will not
		249	contain any 8 bit characters.
164		250
165	JSON::XS->new->ascii (1)->encode ([chr 0x10401])	251	JSON::XS->new->ascii (1)->encode ([chr 0x10401])
166	=> ["\ud801\udc01"]	252	=> ["\ud801\udc01"]
167		253
		254	=item $json = $json->latin1 ([$enable])
		255
		256	=item $enabled = $json->get_latin1
		257
		258	If C<$enable> is true (or missing), then the C<encode> method will encode
		259	the resulting JSON text as latin1 (or iso-8859-1), escaping any characters
		260	outside the code range C<0..255>. The resulting string can be treated as a
		261	latin1-encoded JSON text or a native Unicode string. The C<decode> method
		262	will not be affected in any way by this flag, as C<decode> by default
		263	expects Unicode, which is a strict superset of latin1.
		264
		265	If C<$enable> is false, then the C<encode> method will not escape Unicode
		266	characters unless required by the JSON syntax or other flags.
		267
		268	The main use for this flag is efficiently encoding binary data as JSON
		269	text, as most octets will not be escaped, resulting in a smaller encoded
		270	size. The disadvantage is that the resulting JSON text is encoded
		271	in latin1 (and must correctly be treated as such when storing and
		272	transferring), a rare encoding for JSON. It is therefore most useful when
		273	you want to store data structures known to contain binary data efficiently
		274	in files or databases, not when talking to other JSON encoders/decoders.
		275
		276	JSON::XS->new->latin1->encode (["\x{89}\x{abc}"]
		277	=> ["\x{89}\\u0abc"] # (perl syntax, U+abc escaped, U+89 not)
		278
168	=item $json = $json->utf8 ([$enable])	279	=item $json = $json->utf8 ([$enable])
		280
		281	=item $enabled = $json->get_utf8
169		282
170	If C<$enable> is true (or missing), then the C<encode> method will encode	283	If C<$enable> is true (or missing), then the C<encode> method will encode
171	the JSON result into UTF-8, as required by many protocols, while the	284	the JSON result into UTF-8, as required by many protocols, while the
172	C<decode> method expects to be handled an UTF-8-encoded string. Please	285	C<decode> method expects to be handled an UTF-8-encoded string. Please
173	note that UTF-8-encoded strings do not contain any characters outside the	286	note that UTF-8-encoded strings do not contain any characters outside the
174	range C<0..255>, they are thus useful for bytewise/binary I/O. In future	287	range C<0..255>, they are thus useful for bytewise/binary I/O. In future
175	versions, enabling this option might enable autodetection of the UTF-16	288	versions, enabling this option might enable autodetection of the UTF-16
176	and UTF-32 encoding families, as described in RFC4627.	289	and UTF-32 encoding families, as described in RFC4627.
177		290
178	If C<$enable> is false, then the C<encode> method will return the JSON	291	If C<$enable> is false, then the C<encode> method will return the JSON
179	string as a (non-encoded) unicode string, while C<decode> expects thus a	292	string as a (non-encoded) Unicode string, while C<decode> expects thus a
180	unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs	293	Unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs
181	to be done yourself, e.g. using the Encode module.	294	to be done yourself, e.g. using the Encode module.
182		295
183	Example, output UTF-16BE-encoded JSON:	296	Example, output UTF-16BE-encoded JSON:
184		297
185	use Encode;	298	use Encode;
…		…
207	]	320	]
208	}	321	}
209		322
210	=item $json = $json->indent ([$enable])	323	=item $json = $json->indent ([$enable])
211		324
		325	=item $enabled = $json->get_indent
		326
212	If C<$enable> is true (or missing), then the C<encode> method will use a multiline	327	If C<$enable> is true (or missing), then the C<encode> method will use a multiline
213	format as output, putting every array member or object/hash key-value pair	328	format as output, putting every array member or object/hash key-value pair
214	into its own line, identing them properly.	329	into its own line, indenting them properly.
215		330
216	If C<$enable> is false, no newlines or indenting will be produced, and the	331	If C<$enable> is false, no newlines or indenting will be produced, and the
217	resulting JSON text is guarenteed not to contain any C<newlines>.	332	resulting JSON text is guaranteed not to contain any C<newlines>.
218		333
219	This setting has no effect when decoding JSON texts.	334	This setting has no effect when decoding JSON texts.
220		335
221	=item $json = $json->space_before ([$enable])	336	=item $json = $json->space_before ([$enable])
		337
		338	=item $enabled = $json->get_space_before
222		339
223	If C<$enable> is true (or missing), then the C<encode> method will add an extra	340	If C<$enable> is true (or missing), then the C<encode> method will add an extra
224	optional space before the C<:> separating keys from values in JSON objects.	341	optional space before the C<:> separating keys from values in JSON objects.
225		342
226	If C<$enable> is false, then the C<encode> method will not add any extra	343	If C<$enable> is false, then the C<encode> method will not add any extra
…		…
232	Example, space_before enabled, space_after and indent disabled:	349	Example, space_before enabled, space_after and indent disabled:
233		350
234	{"key" :"value"}	351	{"key" :"value"}
235		352
236	=item $json = $json->space_after ([$enable])	353	=item $json = $json->space_after ([$enable])
		354
		355	=item $enabled = $json->get_space_after
237		356
238	If C<$enable> is true (or missing), then the C<encode> method will add an extra	357	If C<$enable> is true (or missing), then the C<encode> method will add an extra
239	optional space after the C<:> separating keys from values in JSON objects	358	optional space after the C<:> separating keys from values in JSON objects
240	and extra whitespace after the C<,> separating key-value pairs and array	359	and extra whitespace after the C<,> separating key-value pairs and array
241	members.	360	members.
…		…
247		366
248	Example, space_before and indent disabled, space_after enabled:	367	Example, space_before and indent disabled, space_after enabled:
249		368
250	{"key": "value"}	369	{"key": "value"}
251		370
		371	=item $json = $json->relaxed ([$enable])
		372
		373	=item $enabled = $json->get_relaxed
		374
		375	If C<$enable> is true (or missing), then C<decode> will accept some
		376	extensions to normal JSON syntax (see below). C<encode> will not be
		377	affected in anyway. I<Be aware that this option makes you accept invalid
		378	JSON texts as if they were valid!>. I suggest only to use this option to
		379	parse application-specific files written by humans (configuration files,
		380	resource files etc.)
		381
		382	If C<$enable> is false (the default), then C<decode> will only accept
		383	valid JSON texts.
		384
		385	Currently accepted extensions are:
		386
		387	=over 4
		388
		389	=item * list items can have an end-comma
		390
		391	JSON I<separates> array elements and key-value pairs with commas. This
		392	can be annoying if you write JSON texts manually and want to be able to
		393	quickly append elements, so this extension accepts comma at the end of
		394	such items not just between them:
		395
		396	[
		397	1,
		398	2, <- this comma not normally allowed
		399	]
		400	{
		401	"k1": "v1",
		402	"k2": "v2", <- this comma not normally allowed
		403	}
		404
		405	=item * shell-style '#'-comments
		406
		407	Whenever JSON allows whitespace, shell-style comments are additionally
		408	allowed. They are terminated by the first carriage-return or line-feed
		409	character, after which more white-space and comments are allowed.
		410
		411	[
		412	1, # this comment not allowed in JSON
		413	# neither this one...
		414	]
		415
		416	=back
		417
252	=item $json = $json->canonical ([$enable])	418	=item $json = $json->canonical ([$enable])
		419
		420	=item $enabled = $json->get_canonical
253		421
254	If C<$enable> is true (or missing), then the C<encode> method will output JSON objects	422	If C<$enable> is true (or missing), then the C<encode> method will output JSON objects
255	by sorting their keys. This is adding a comparatively high overhead.	423	by sorting their keys. This is adding a comparatively high overhead.
256		424
257	If C<$enable> is false, then the C<encode> method will output key-value	425	If C<$enable> is false, then the C<encode> method will output key-value
258	pairs in the order Perl stores them (which will likely change between runs	426	pairs in the order Perl stores them (which will likely change between runs
259	of the same script).	427	of the same script).
260		428
261	This option is useful if you want the same data structure to be encoded as	429	This option is useful if you want the same data structure to be encoded as
262	the same JSON text (given the same overall settings). If it is disabled,	430	the same JSON text (given the same overall settings). If it is disabled,
263	the same hash migh be encoded differently even if contains the same data,	431	the same hash might be encoded differently even if contains the same data,
264	as key-value pairs have no inherent ordering in Perl.	432	as key-value pairs have no inherent ordering in Perl.
265		433
266	This setting has no effect when decoding JSON texts.	434	This setting has no effect when decoding JSON texts.
267		435
268	=item $json = $json->allow_nonref ([$enable])	436	=item $json = $json->allow_nonref ([$enable])
		437
		438	=item $enabled = $json->get_allow_nonref
269		439
270	If C<$enable> is true (or missing), then the C<encode> method can convert a	440	If C<$enable> is true (or missing), then the C<encode> method can convert a
271	non-reference into its corresponding string, number or null JSON value,	441	non-reference into its corresponding string, number or null JSON value,
272	which is an extension to RFC4627. Likewise, C<decode> will accept those JSON	442	which is an extension to RFC4627. Likewise, C<decode> will accept those JSON
273	values instead of croaking.	443	values instead of croaking.
…		…
281	resulting in an invalid JSON text:	451	resulting in an invalid JSON text:
282		452
283	JSON::XS->new->allow_nonref->encode ("Hello, World!")	453	JSON::XS->new->allow_nonref->encode ("Hello, World!")
284	=> "Hello, World!"	454	=> "Hello, World!"
285		455
		456	=item $json = $json->allow_blessed ([$enable])
		457
		458	=item $enabled = $json->get_allow_blessed
		459
		460	If C<$enable> is true (or missing), then the C<encode> method will not
		461	barf when it encounters a blessed reference. Instead, the value of the
		462	B<convert_blessed> option will decide whether C<null> (C<convert_blessed>
		463	disabled or no C<TO_JSON> method found) or a representation of the
		464	object (C<convert_blessed> enabled and C<TO_JSON> method found) is being
		465	encoded. Has no effect on C<decode>.
		466
		467	If C<$enable> is false (the default), then C<encode> will throw an
		468	exception when it encounters a blessed object.
		469
		470	=item $json = $json->convert_blessed ([$enable])
		471
		472	=item $enabled = $json->get_convert_blessed
		473
		474	If C<$enable> is true (or missing), then C<encode>, upon encountering a
		475	blessed object, will check for the availability of the C<TO_JSON> method
		476	on the object's class. If found, it will be called in scalar context
		477	and the resulting scalar will be encoded instead of the object. If no
		478	C<TO_JSON> method is found, the value of C<allow_blessed> will decide what
		479	to do.
		480
		481	The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON>
		482	returns other blessed objects, those will be handled in the same
		483	way. C<TO_JSON> must take care of not causing an endless recursion cycle
		484	(== crash) in this case. The name of C<TO_JSON> was chosen because other
		485	methods called by the Perl core (== not by the user of the object) are
		486	usually in upper case letters and to avoid collisions with any C<to_json>
		487	function or method.
		488
		489	This setting does not yet influence C<decode> in any way, but in the
		490	future, global hooks might get installed that influence C<decode> and are
		491	enabled by this setting.
		492
		493	If C<$enable> is false, then the C<allow_blessed> setting will decide what
		494	to do when a blessed object is found.
		495
		496	=item $json = $json->filter_json_object ([$coderef->($hashref)])
		497
		498	When C<$coderef> is specified, it will be called from C<decode> each
		499	time it decodes a JSON object. The only argument is a reference to the
		500	newly-created hash. If the code references returns a single scalar (which
		501	need not be a reference), this value (i.e. a copy of that scalar to avoid
		502	aliasing) is inserted into the deserialised data structure. If it returns
		503	an empty list (NOTE: I<not> C<undef>, which is a valid scalar), the
		504	original deserialised hash will be inserted. This setting can slow down
		505	decoding considerably.
		506
		507	When C<$coderef> is omitted or undefined, any existing callback will
		508	be removed and C<decode> will not change the deserialised hash in any
		509	way.
		510
		511	Example, convert all JSON objects into the integer 5:
		512
		513	my $js = JSON::XS->new->filter_json_object (sub { 5 });
		514	# returns [5]
		515	$js->decode ('[{}]')
		516	# throw an exception because allow_nonref is not enabled
		517	# so a lone 5 is not allowed.
		518	$js->decode ('{"a":1, "b":2}');
		519
		520	=item $json = $json->filter_json_single_key_object ($key [=> $coderef->($value)])
		521
		522	Works remotely similar to C<filter_json_object>, but is only called for
		523	JSON objects having a single key named C<$key>.
		524
		525	This C<$coderef> is called before the one specified via
		526	C<filter_json_object>, if any. It gets passed the single value in the JSON
		527	object. If it returns a single value, it will be inserted into the data
		528	structure. If it returns nothing (not even C<undef> but the empty list),
		529	the callback from C<filter_json_object> will be called next, as if no
		530	single-key callback were specified.
		531
		532	If C<$coderef> is omitted or undefined, the corresponding callback will be
		533	disabled. There can only ever be one callback for a given key.
		534
		535	As this callback gets called less often then the C<filter_json_object>
		536	one, decoding speed will not usually suffer as much. Therefore, single-key
		537	objects make excellent targets to serialise Perl objects into, especially
		538	as single-key JSON objects are as close to the type-tagged value concept
		539	as JSON gets (it's basically an ID/VALUE tuple). Of course, JSON does not
		540	support this in any way, so you need to make sure your data never looks
		541	like a serialised Perl hash.
		542
		543	Typical names for the single object key are C<__class_whatever__>, or
		544	C<$__dollars_are_rarely_used__$> or C<}ugly_brace_placement>, or even
		545	things like C<__class_md5sum(classname)__>, to reduce the risk of clashing
		546	with real hashes.
		547
		548	Example, decode JSON objects of the form C<< { "__widget__" => <id> } >>
		549	into the corresponding C<< $WIDGET{<id>} >> object:
		550
		551	# return whatever is in $WIDGET{5}:
		552	JSON::XS
		553	->new
		554	->filter_json_single_key_object (__widget__ => sub {
		555	$WIDGET{ $_[0] }
		556	})
		557	->decode ('{"__widget__": 5')
		558
		559	# this can be used with a TO_JSON method in some "widget" class
		560	# for serialisation to json:
		561	sub WidgetBase::TO_JSON {
		562	my ($self) = @_;
		563
		564	unless ($self->{id}) {
		565	$self->{id} = ..get..some..id..;
		566	$WIDGET{$self->{id}} = $self;
		567	}
		568
		569	{ __widget__ => $self->{id} }
		570	}
		571
286	=item $json = $json->shrink ([$enable])	572	=item $json = $json->shrink ([$enable])
		573
		574	=item $enabled = $json->get_shrink
287		575
288	Perl usually over-allocates memory a bit when allocating space for	576	Perl usually over-allocates memory a bit when allocating space for
289	strings. This flag optionally resizes strings generated by either	577	strings. This flag optionally resizes strings generated by either
290	C<encode> or C<decode> to their minimum size possible. This can save	578	C<encode> or C<decode> to their minimum size possible. This can save
291	memory when your JSON texts are either very very long or you have many	579	memory when your JSON texts are either very very long or you have many
…		…
309	strings that look like integers or floats into integers or floats	597	strings that look like integers or floats into integers or floats
310	internally (there is no difference on the Perl level), saving space.	598	internally (there is no difference on the Perl level), saving space.
311		599
312	=item $json = $json->max_depth ([$maximum_nesting_depth])	600	=item $json = $json->max_depth ([$maximum_nesting_depth])
313		601
		602	=item $max_depth = $json->get_max_depth
		603
314	Sets the maximum nesting level (default C<4096>) accepted while encoding	604	Sets the maximum nesting level (default C<512>) accepted while encoding
315	or decoding. If the JSON text or Perl data structure has an equal or	605	or decoding. If the JSON text or Perl data structure has an equal or
316	higher nesting level then this limit, then the encoder and decoder will	606	higher nesting level then this limit, then the encoder and decoder will
317	stop and croak at that point.	607	stop and croak at that point.
318		608
319	Nesting level is defined by number of hash- or arrayrefs that the encoder	609	Nesting level is defined by number of hash- or arrayrefs that the encoder
…		…
322	given character in a string.	612	given character in a string.
323		613
324	Setting the maximum depth to one disallows any nesting, so that ensures	614	Setting the maximum depth to one disallows any nesting, so that ensures
325	that the object is only a single hash/object or array.	615	that the object is only a single hash/object or array.
326		616
327	The argument to C<max_depth> will be rounded up to the next nearest power	617	The argument to C<max_depth> will be rounded up to the next highest power
328	of two.	618	of two. If no argument is given, the highest possible setting will be
		619	used, which is rarely useful.
		620
		621	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
		622
		623	=item $json = $json->max_size ([$maximum_string_size])
		624
		625	=item $max_size = $json->get_max_size
		626
		627	Set the maximum length a JSON text may have (in bytes) where decoding is
		628	being attempted. The default is C<0>, meaning no limit. When C<decode>
		629	is called on a string longer then this number of characters it will not
		630	attempt to decode the string but throw an exception. This setting has no
		631	effect on C<encode> (yet).
		632
		633	The argument to C<max_size> will be rounded up to the next B<highest>
		634	power of two (so may be more than requested). If no argument is given, the
		635	limit check will be deactivated (same as when C<0> is specified).
329		636
330	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.	637	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
331		638
332	=item $json_text = $json->encode ($perl_scalar)	639	=item $json_text = $json->encode ($perl_scalar)
333		640
…		…
345		652
346	JSON numbers and strings become simple Perl scalars. JSON arrays become	653	JSON numbers and strings become simple Perl scalars. JSON arrays become
347	Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes	654	Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes
348	C<1>, C<false> becomes C<0> and C<null> becomes C<undef>.	655	C<1>, C<false> becomes C<0> and C<null> becomes C<undef>.
349		656
		657	=item ($perl_scalar, $characters) = $json->decode_prefix ($json_text)
		658
		659	This works like the C<decode> method, but instead of raising an exception
		660	when there is trailing garbage after the first JSON object, it will
		661	silently stop parsing there and return the number of characters consumed
		662	so far.
		663
		664	This is useful if your JSON texts are not delimited by an outer protocol
		665	(which is not the brightest thing to do in the first place) and you need
		666	to know where the JSON text ends.
		667
		668	JSON::XS->new->decode_prefix ("[1] the tail")
		669	=> ([], 3)
		670
350	=back	671	=back
351		672
352		673
353	=head1 MAPPING	674	=head1 MAPPING
354		675
…		…
356	vice versa. These mappings are designed to "do the right thing" in most	677	vice versa. These mappings are designed to "do the right thing" in most
357	circumstances automatically, preserving round-tripping characteristics	678	circumstances automatically, preserving round-tripping characteristics
358	(what you put in comes out as something equivalent).	679	(what you put in comes out as something equivalent).
359		680
360	For the more enlightened: note that in the following descriptions,	681	For the more enlightened: note that in the following descriptions,
361	lowercase I<perl> refers to the Perl interpreter, while uppcercase I<Perl>	682	lowercase I<perl> refers to the Perl interpreter, while uppercase I<Perl>
362	refers to the abstract Perl language itself.	683	refers to the abstract Perl language itself.
363		684
		685
364	=head2 JSON -> PERL	686	=head2 JSON -> PERL
365		687
366	=over 4	688	=over 4
367		689
368	=item object	690	=item object
369		691
370	A JSON object becomes a reference to a hash in Perl. No ordering of object	692	A JSON object becomes a reference to a hash in Perl. No ordering of object
371	keys is preserved (JSON does not preserver object key ordering itself).	693	keys is preserved (JSON does not preserve object key ordering itself).
372		694
373	=item array	695	=item array
374		696
375	A JSON array becomes a reference to an array in Perl.	697	A JSON array becomes a reference to an array in Perl.
376		698
…		…
380	are represented by the same codepoints in the Perl string, so no manual	702	are represented by the same codepoints in the Perl string, so no manual
381	decoding is necessary.	703	decoding is necessary.
382		704
383	=item number	705	=item number
384		706
385	A JSON number becomes either an integer or numeric (floating point)	707	A JSON number becomes either an integer, numeric (floating point) or
386	scalar in perl, depending on its range and any fractional parts. On the	708	string scalar in perl, depending on its range and any fractional parts. On
387	Perl level, there is no difference between those as Perl handles all the	709	the Perl level, there is no difference between those as Perl handles all
388	conversion details, but an integer may take slightly less memory and might	710	the conversion details, but an integer may take slightly less memory and
389	represent more values exactly than (floating point) numbers.	711	might represent more values exactly than (floating point) numbers.
		712
		713	If the number consists of digits only, JSON::XS will try to represent
		714	it as an integer value. If that fails, it will try to represent it as
		715	a numeric (floating point) value if that is possible without loss of
		716	precision. Otherwise it will preserve the number as a string value.
		717
		718	Numbers containing a fractional or exponential part will always be
		719	represented as numeric (floating point) values, possibly at a loss of
		720	precision.
		721
		722	This might create round-tripping problems as numbers might become strings,
		723	but as Perl is typeless there is no other way to do it.
390		724
391	=item true, false	725	=item true, false
392		726
393	These JSON atoms become C<0>, C<1>, respectively. Information is lost in	727	These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>,
394	this process. Future versions might represent those values differently,	728	respectively. They are overloaded to act almost exactly like the numbers
395	but they will be guarenteed to act like these integers would normally in	729	C<1> and C<0>. You can check whether a scalar is a JSON boolean by using
396	Perl.	730	the C<JSON::XS::is_bool> function.
397		731
398	=item null	732	=item null
399		733
400	A JSON null atom becomes C<undef> in Perl.	734	A JSON null atom becomes C<undef> in Perl.
401		735
402	=back	736	=back
		737
403		738
404	=head2 PERL -> JSON	739	=head2 PERL -> JSON
405		740
406	The mapping from Perl to JSON is slightly more difficult, as Perl is a	741	The mapping from Perl to JSON is slightly more difficult, as Perl is a
407	truly typeless language, so we can only guess which JSON type is meant by	742	truly typeless language, so we can only guess which JSON type is meant by
…		…
430	Other unblessed references are generally not allowed and will cause an	765	Other unblessed references are generally not allowed and will cause an
431	exception to be thrown, except for references to the integers C<0> and	766	exception to be thrown, except for references to the integers C<0> and
432	C<1>, which get turned into C<false> and C<true> atoms in JSON. You can	767	C<1>, which get turned into C<false> and C<true> atoms in JSON. You can
433	also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability.	768	also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability.
434		769
435	to_json [\0,JSON::XS::true] # yields [false,true]	770	encode_json [\0,JSON::XS::true] # yields [false,true]
		771
		772	=item JSON::XS::true, JSON::XS::false
		773
		774	These special values become JSON true and JSON false values,
		775	respectively. You can also use C<\1> and C<\0> directly if you want.
436		776
437	=item blessed objects	777	=item blessed objects
438		778
439	Blessed objects are not allowed. JSON::XS currently tries to encode their	779	Blessed objects are not directly representable in JSON. See the
440	underlying representation (hash- or arrayref), but this behaviour might	780	C<allow_blessed> and C<convert_blessed> methods on various options on
441	change in future versions.	781	how to deal with this: basically, you can choose between throwing an
		782	exception, encoding the reference as if it weren't blessed, or provide
		783	your own serialiser method.
442		784
443	=item simple scalars	785	=item simple scalars
444		786
445	Simple Perl scalars (any scalar that is not a reference) are the most	787	Simple Perl scalars (any scalar that is not a reference) are the most
446	difficult objects to encode: JSON::XS will encode undefined scalars as	788	difficult objects to encode: JSON::XS will encode undefined scalars as
447	JSON null value, scalars that have last been used in a string context	789	JSON C<null> values, scalars that have last been used in a string context
448	before encoding as JSON strings and anything else as number value:	790	before encoding as JSON strings, and anything else as number value:
449		791
450	# dump as number	792	# dump as number
451	to_json [2] # yields [2]	793	encode_json [2] # yields [2]
452	to_json [-3.0e17] # yields [-3e+17]	794	encode_json [-3.0e17] # yields [-3e+17]
453	my $value = 5; to_json [$value] # yields [5]	795	my $value = 5; encode_json [$value] # yields [5]
454		796
455	# used as string, so dump as string	797	# used as string, so dump as string
456	print $value;	798	print $value;
457	to_json [$value] # yields ["5"]	799	encode_json [$value] # yields ["5"]
458		800
459	# undef becomes null	801	# undef becomes null
460	to_json [undef] # yields [null]	802	encode_json [undef] # yields [null]
461		803
462	You can force the type to be a string by stringifying it:	804	You can force the type to be a JSON string by stringifying it:
463		805
464	my $x = 3.1; # some variable containing a number	806	my $x = 3.1; # some variable containing a number
465	"$x"; # stringified	807	"$x"; # stringified
466	$x .= ""; # another, more awkward way to stringify	808	$x .= ""; # another, more awkward way to stringify
467	print $x; # perl does it for you, too, quite often	809	print $x; # perl does it for you, too, quite often
468		810
469	You can force the type to be a number by numifying it:	811	You can force the type to be a JSON number by numifying it:
470		812
471	my $x = "3"; # some variable containing a string	813	my $x = "3"; # some variable containing a string
472	$x += 0; # numify it, ensuring it will be dumped as a number	814	$x += 0; # numify it, ensuring it will be dumped as a number
473	$x *= 1; # same thing, the choise is yours.	815	$x *= 1; # same thing, the choice is yours.
474		816
475	You can not currently output JSON booleans or force the type in other,	817	You can not currently force the type in other, less obscure, ways. Tell me
476	less obscure, ways. Tell me if you need this capability.	818	if you need this capability (but don't forget to explain why its needed
477		819	:).
478	=item circular data structures
479
480	Those will be encoded until memory or stackspace runs out.
481		820
482	=back	821	=back
483		822
484		823
485	=head1 COMPARISON	824	=head1 COMPARISON
…		…
494		833
495	=item JSON 1.07	834	=item JSON 1.07
496		835
497	Slow (but very portable, as it is written in pure Perl).	836	Slow (but very portable, as it is written in pure Perl).
498		837
499	Undocumented/buggy Unicode handling (how JSON handles unicode values is	838	Undocumented/buggy Unicode handling (how JSON handles Unicode values is
500	undocumented. One can get far by feeding it unicode strings and doing	839	undocumented. One can get far by feeding it Unicode strings and doing
501	en-/decoding oneself, but unicode escapes are not working properly).	840	en-/decoding oneself, but Unicode escapes are not working properly).
502		841
503	No roundtripping (strings get clobbered if they look like numbers, e.g.	842	No round-tripping (strings get clobbered if they look like numbers, e.g.
504	the string C<2.0> will encode to C<2.0> instead of C<"2.0">, and that will	843	the string C<2.0> will encode to C<2.0> instead of C<"2.0">, and that will
505	decode into the number 2.	844	decode into the number 2.
506		845
507	=item JSON::PC 0.01	846	=item JSON::PC 0.01
508		847
509	Very fast.	848	Very fast.
510		849
511	Undocumented/buggy Unicode handling.	850	Undocumented/buggy Unicode handling.
512		851
513	No roundtripping.	852	No round-tripping.
514		853
515	Has problems handling many Perl values (e.g. regex results and other magic	854	Has problems handling many Perl values (e.g. regex results and other magic
516	values will make it croak).	855	values will make it croak).
517		856
518	Does not even generate valid JSON (C<{1,2}> gets converted to C<{1:2}>	857	Does not even generate valid JSON (C<{1,2}> gets converted to C<{1:2}>
…		…
528	Very inflexible (no human-readable format supported, format pretty much	867	Very inflexible (no human-readable format supported, format pretty much
529	undocumented. I need at least a format for easy reading by humans and a	868	undocumented. I need at least a format for easy reading by humans and a
530	single-line compact format for use in a protocol, and preferably a way to	869	single-line compact format for use in a protocol, and preferably a way to
531	generate ASCII-only JSON texts).	870	generate ASCII-only JSON texts).
532		871
533	Completely broken (and confusingly documented) Unicode handling (unicode	872	Completely broken (and confusingly documented) Unicode handling (Unicode
534	escapes are not working properly, you need to set ImplicitUnicode to	873	escapes are not working properly, you need to set ImplicitUnicode to
535	I<different> values on en- and decoding to get symmetric behaviour).	874	I<different> values on en- and decoding to get symmetric behaviour).
536		875
537	No roundtripping (simple cases work, but this depends on wether the scalar	876	No round-tripping (simple cases work, but this depends on whether the scalar
538	value was used in a numeric context or not).	877	value was used in a numeric context or not).
539		878
540	Dumping hashes may skip hash values depending on iterator state.	879	Dumping hashes may skip hash values depending on iterator state.
541		880
542	Unmaintained (maintainer unresponsive for many months, bugs are not	881	Unmaintained (maintainer unresponsive for many months, bugs are not
543	getting fixed).	882	getting fixed).
544		883
545	Does not check input for validity (i.e. will accept non-JSON input and	884	Does not check input for validity (i.e. will accept non-JSON input and
546	return "something" instead of raising an exception. This is a security	885	return "something" instead of raising an exception. This is a security
547	issue: imagine two banks transfering money between each other using	886	issue: imagine two banks transferring money between each other using
548	JSON. One bank might parse a given non-JSON request and deduct money,	887	JSON. One bank might parse a given non-JSON request and deduct money,
549	while the other might reject the transaction with a syntax error. While a	888	while the other might reject the transaction with a syntax error. While a
550	good protocol will at least recover, that is extra unnecessary work and	889	good protocol will at least recover, that is extra unnecessary work and
551	the transaction will still not succeed).	890	the transaction will still not succeed).
552		891
553	=item JSON::DWIW 0.04	892	=item JSON::DWIW 0.04
554		893
555	Very fast. Very natural. Very nice.	894	Very fast. Very natural. Very nice.
556		895
557	Undocumented unicode handling (but the best of the pack. Unicode escapes	896	Undocumented Unicode handling (but the best of the pack. Unicode escapes
558	still don't get parsed properly).	897	still don't get parsed properly).
559		898
560	Very inflexible.	899	Very inflexible.
561		900
562	No roundtripping.	901	No round-tripping.
563		902
564	Does not generate valid JSON texts (key strings are often unquoted, empty keys	903	Does not generate valid JSON texts (key strings are often unquoted, empty keys
565	result in nothing being output)	904	result in nothing being output)
566		905
567	Does not check input for validity.	906	Does not check input for validity.
568		907
569	=back	908	=back
		909
		910
		911	=head2 JSON and YAML
		912
		913	You often hear that JSON is a subset of YAML. This is, however, a mass
		914	hysteria(*) and very far from the truth. In general, there is no way to
		915	configure JSON::XS to output a data structure as valid YAML that works for
		916	all cases.
		917
		918	If you really must use JSON::XS to generate YAML, you should use this
		919	algorithm (subject to change in future versions):
		920
		921	my $to_yaml = JSON::XS->new->utf8->space_after (1);
		922	my $yaml = $to_yaml->encode ($ref) . "\n";
		923
		924	This will I<usually> generate JSON texts that also parse as valid
		925	YAML. Please note that YAML has hardcoded limits on (simple) object key
		926	lengths that JSON doesn't have and also has different and incompatible
		927	unicode handling, so you should make sure that your hash keys are
		928	noticeably shorter than the 1024 "stream characters" YAML allows and that
		929	you do not have codepoints with values outside the Unicode BMP (basic
		930	multilingual page). YAML also does not allow C<\/> sequences in strings
		931	(which JSON::XS does not I<currently> generate).
		932
		933	There might be other incompatibilities that I am not aware of (or the YAML
		934	specification has been changed yet again - it does so quite often). In
		935	general you should not try to generate YAML with a JSON generator or vice
		936	versa, or try to parse JSON with a YAML parser or vice versa: chances are
		937	high that you will run into severe interoperability problems when you
		938	least expect it.
		939
		940	=over 4
		941
		942	=item (*)
		943
		944	This is spread actively by the YAML team, however. For many years now they
		945	claim YAML were a superset of JSON, even when proven otherwise.
		946
		947	Even the author of this manpage was at some point accused of providing
		948	"incorrect" information, despite the evidence presented (claims ranged
		949	from "your documentation contains inaccurate and negative statements about
		950	YAML" (the only negative comment is this footnote, and it didn't exist
		951	back then; the question on which claims were inaccurate was never answered
		952	etc.) to "the YAML spec is not up-to-date" (the real and supposedly
		953	JSON-compatible spec is apparently not currently publicly available)
		954	to actual requests to replace this section by incorrect information,
		955	suppressing information about the real problem).
		956
		957	So whenever you are told that YAML was a superset of JSON, first check
		958	wether it is really true (it might be when you check it, but it certainly
		959	was not true when this was written). I would much prefer if the YAML team
		960	would spent their time on actually making JSON compatibility a truth
		961	(JSON, after all, has a very small and simple specification) instead of
		962	trying to lobby/force people into reporting untruths.
		963
		964	=back
		965
570		966
571	=head2 SPEED	967	=head2 SPEED
572		968
573	It seems that JSON::XS is surprisingly fast, as shown in the following	969	It seems that JSON::XS is surprisingly fast, as shown in the following
574	tables. They have been generated with the help of the C<eg/bench> program	970	tables. They have been generated with the help of the C<eg/bench> program
575	in the JSON::XS distribution, to make it easy to compare on your own	971	in the JSON::XS distribution, to make it easy to compare on your own
576	system.	972	system.
577		973
578	First comes a comparison between various modules using a very short JSON	974	First comes a comparison between various modules using a very short
579	string:	975	single-line JSON string:
580		976
581	{"method": "handleMessage", "params": ["user1", "we were just talking"], "id": null}	977	{"method": "handleMessage", "params": ["user1", "we were just talking"], \
		978	"id": null, "array":[1,11,234,-5,1e5,1e7, true, false]}
582		979
583	It shows the number of encodes/decodes per second (JSON::XS uses the	980	It shows the number of encodes/decodes per second (JSON::XS uses
584	functional interface, while JSON::XS/2 uses the OO interface with	981	the functional interface, while JSON::XS/2 uses the OO interface
585	pretty-printing and hashkey sorting enabled). Higher is better:	982	with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables
		983	shrink). Higher is better:
586		984
587	module \| encode \| decode \|	985	module \| encode \| decode \|
588	-----------\|------------\|------------\|	986	-----------\|------------\|------------\|
589	JSON \| 11488.516 \| 7823.035 \|	987	JSON 1.x \| 4990.842 \| 4088.813 \|
590	JSON::DWIW \| 94708.054 \| 129094.260 \|	988	JSON::DWIW \| 51653.990 \| 71575.154 \|
591	JSON::PC \| 63884.157 \| 128528.212 \|	989	JSON::PC \| 65948.176 \| 74631.744 \|
592	JSON::Syck \| 34898.677 \| 42096.911 \|	990	JSON::PP \| 8931.652 \| 3817.168 \|
593	JSON::XS \| 654027.064 \| 396423.669 \|	991	JSON::Syck \| 24877.248 \| 27776.848 \|
594	JSON::XS/2 \| 371564.190 \| 371725.613 \|	992	JSON::XS \| 388361.481 \| 227951.304 \|
		993	JSON::XS/2 \| 227951.304 \| 218453.333 \|
		994	JSON::XS/3 \| 338250.323 \| 218453.333 \|
		995	Storable \| 16500.016 \| 135300.129 \|
595	-----------+------------+------------+	996	-----------+------------+------------+
596		997
597	That is, JSON::XS is more than six times faster than JSON::DWIW on	998	That is, JSON::XS is about five times faster than JSON::DWIW on encoding,
598	encoding, more than three times faster on decoding, and about thirty times	999	about three times faster on decoding, and over forty times faster
599	faster than JSON, even with pretty-printing and key sorting.	1000	than JSON, even with pretty-printing and key sorting. It also compares
		1001	favourably to Storable for small amounts of data.
600		1002
601	Using a longer test string (roughly 18KB, generated from Yahoo! Locals	1003	Using a longer test string (roughly 18KB, generated from Yahoo! Locals
602	search API (http://nanoref.com/yahooapis/mgPdGg):	1004	search API (http://nanoref.com/yahooapis/mgPdGg):
603		1005
604	module \| encode \| decode \|	1006	module \| encode \| decode \|
605	-----------\|------------\|------------\|	1007	-----------\|------------\|------------\|
606	JSON \| 273.023 \| 44.674 \|	1008	JSON 1.x \| 55.260 \| 34.971 \|
607	JSON::DWIW \| 1089.383 \| 1145.704 \|	1009	JSON::DWIW \| 825.228 \| 1082.513 \|
608	JSON::PC \| 3097.419 \| 2393.921 \|	1010	JSON::PC \| 3571.444 \| 2394.829 \|
609	JSON::Syck \| 514.060 \| 843.053 \|	1011	JSON::PP \| 210.987 \| 32.574 \|
610	JSON::XS \| 6479.668 \| 3636.364 \|	1012	JSON::Syck \| 552.551 \| 787.544 \|
611	JSON::XS/2 \| 3774.221 \| 3599.124 \|	1013	JSON::XS \| 5780.463 \| 4854.519 \|
		1014	JSON::XS/2 \| 3869.998 \| 4798.975 \|
		1015	JSON::XS/3 \| 5862.880 \| 4798.975 \|
		1016	Storable \| 4445.002 \| 5235.027 \|
612	-----------+------------+------------+	1017	-----------+------------+------------+
613		1018
614	Again, JSON::XS leads by far.	1019	Again, JSON::XS leads by far (except for Storable which non-surprisingly
		1020	decodes faster).
615		1021
616	On large strings containing lots of high unicode characters, some modules	1022	On large strings containing lots of high Unicode characters, some modules
617	(such as JSON::PC) seem to decode faster than JSON::XS, but the result	1023	(such as JSON::PC) seem to decode faster than JSON::XS, but the result
618	will be broken due to missing (or wrong) unicode handling. Others refuse	1024	will be broken due to missing (or wrong) Unicode handling. Others refuse
619	to decode or encode properly, so it was impossible to prepare a fair	1025	to decode or encode properly, so it was impossible to prepare a fair
620	comparison table for that case.	1026	comparison table for that case.
621		1027
622		1028
623	=head1 SECURITY CONSIDERATIONS	1029	=head1 SECURITY CONSIDERATIONS
…		…
629	any buffer overflows. Obviously, this module should ensure that and I am	1035	any buffer overflows. Obviously, this module should ensure that and I am
630	trying hard on making that true, but you never know.	1036	trying hard on making that true, but you never know.
631		1037
632	Second, you need to avoid resource-starving attacks. That means you should	1038	Second, you need to avoid resource-starving attacks. That means you should
633	limit the size of JSON texts you accept, or make sure then when your	1039	limit the size of JSON texts you accept, or make sure then when your
634	resources run out, thats just fine (e.g. by using a separate process that	1040	resources run out, that's just fine (e.g. by using a separate process that
635	can crash safely). The size of a JSON text in octets or characters is	1041	can crash safely). The size of a JSON text in octets or characters is
636	usually a good indication of the size of the resources required to decode	1042	usually a good indication of the size of the resources required to decode
637	it into a Perl structure.	1043	it into a Perl structure. While JSON::XS can check the size of the JSON
		1044	text, it might be too late when you already have it in memory, so you
		1045	might want to check the size before you accept the string.
638		1046
639	Third, JSON::XS recurses using the C stack when decoding objects and	1047	Third, JSON::XS recurses using the C stack when decoding objects and
640	arrays. The C stack is a limited resource: for instance, on my amd64	1048	arrays. The C stack is a limited resource: for instance, on my amd64
641	machine with 8MB of stack size I can decode around 180k nested arrays	1049	machine with 8MB of stack size I can decode around 180k nested arrays but
642	but only 14k nested JSON objects. If that is exceeded, the program	1050	only 14k nested JSON objects (due to perl itself recursing deeply on croak
643	crashes. Thats why the default nesting limit is set to 4096. If your	1051	to free the temporary). If that is exceeded, the program crashes. To be
		1052	conservative, the default nesting limit is set to 512. If your process
644	process has a smaller stack, you should adjust this setting accordingly	1053	has a smaller stack, you should adjust this setting accordingly with the
645	with the C<max_depth> method.	1054	C<max_depth> method.
646		1055
647	And last but least, something else could bomb you that I forgot to think	1056	And last but least, something else could bomb you that I forgot to think
648	of. In that case, you get to keep the pieces. I am alway sopen for hints,	1057	of. In that case, you get to keep the pieces. I am always open for hints,
649	though...	1058	though...
		1059
		1060	If you are using JSON::XS to return packets to consumption
		1061	by JavaScript scripts in a browser you should have a look at
		1062	L<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether
		1063	you are vulnerable to some common attack vectors (which really are browser
		1064	design bugs, but it is still you who will have to deal with it, as major
		1065	browser developers care only for features, not about getting security
		1066	right).
		1067
		1068
		1069	=head1 THREADS
		1070
		1071	This module is I<not> guaranteed to be thread safe and there are no
		1072	plans to change this until Perl gets thread support (as opposed to the
		1073	horribly slow so-called "threads" which are simply slow and bloated
		1074	process simulations - use fork, its I<much> faster, cheaper, better).
		1075
		1076	(It might actually work, but you have been warned).
650		1077
651		1078
652	=head1 BUGS	1079	=head1 BUGS
653		1080
654	While the goal of this module is to be correct, that unfortunately does	1081	While the goal of this module is to be correct, that unfortunately does
655	not mean its bug-free, only that I think its design is bug-free. It is	1082	not mean its bug-free, only that I think its design is bug-free. It is
656	still relatively early in its development. If you keep reporting bugs they	1083	still relatively early in its development. If you keep reporting bugs they
657	will be fixed swiftly, though.	1084	will be fixed swiftly, though.
658		1085
		1086	Please refrain from using rt.cpan.org or any other bug reporting
		1087	service. I put the contact address into my modules for a reason.
		1088
659	=cut	1089	=cut
660		1090
		1091	our $true = do { bless \(my $dummy = 1), "JSON::XS::Boolean" };
		1092	our $false = do { bless \(my $dummy = 0), "JSON::XS::Boolean" };
		1093
661	sub true() { \1 }	1094	sub true() { $true }
662	sub false() { \0 }	1095	sub false() { $false }
		1096
		1097	sub is_bool($) {
		1098	UNIVERSAL::isa $_[0], "JSON::XS::Boolean"
		1099	# or UNIVERSAL::isa $_[0], "JSON::Literal"
		1100	}
		1101
		1102	XSLoader::load "JSON::XS", $VERSION;
		1103
		1104	package JSON::XS::Boolean;
		1105
		1106	use overload
		1107	"0+" => sub { ${$_[0]} },
		1108	"++" => sub { $_[0] = ${$_[0]} + 1 },
		1109	"--" => sub { $_[0] = ${$_[0]} - 1 },
		1110	fallback => 1;
663		1111
664	1;	1112	1;
665		1113
666	=head1 AUTHOR	1114	=head1 AUTHOR
667		1115

Diff Legend

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

Comparing JSON-XS/XS.pm (file contents): Revision 1.26 by root, Sat Mar 31 14:20:06 2007 UTC vs. Revision 1.83 by root, Sun Jan 20 19:19:07 2008 UTC

Diff Legend

Comparing JSON-XS/XS.pm (file contents):
Revision 1.26 by root, Sat Mar 31 14:20:06 2007 UTC vs.
Revision 1.83 by root, Sun Jan 20 19:19:07 2008 UTC