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

Comparing JSON-XS/XS.pm (file contents):
Revision 1.76 by root, Sun Dec 2 15:34:13 2007 UTC vs.
Revision 1.109 by root, Sat Jul 19 04:21:32 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	=encoding utf-8
4		6
5	JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ	7	JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ
6	(http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html)	8	(http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html)
7		9
8	=head1 SYNOPSIS	10	=head1 SYNOPSIS
10	use JSON::XS;	12	use JSON::XS;
11		13
12	# exported functions, they croak on error	14	# exported functions, they croak on error
13	# and expect/generate UTF-8	15	# and expect/generate UTF-8
14		16
15	$utf8_encoded_json_text = to_json $perl_hash_or_arrayref;	17	$utf8_encoded_json_text = encode_json $perl_hash_or_arrayref;
16	$perl_hash_or_arrayref = from_json $utf8_encoded_json_text;	18	$perl_hash_or_arrayref = decode_json $utf8_encoded_json_text;
17		19
18	# OO-interface	20	# OO-interface
19		21
20	$coder = JSON::XS->new->ascii->pretty->allow_nonref;	22	$coder = JSON::XS->new->ascii->pretty->allow_nonref;
21	$pretty_printed_unencoded = $coder->encode ($perl_scalar);	23	$pretty_printed_unencoded = $coder->encode ($perl_scalar);
22	$perl_scalar = $coder->decode ($unicode_json_text);	24	$perl_scalar = $coder->decode ($unicode_json_text);
23		25
		26	# Note that JSON version 2.0 and above will automatically use JSON::XS
		27	# if available, at virtually no speed overhead either, so you should
		28	# be able to just:
		29
		30	use JSON;
		31
		32	# and do the same things, except that you have a pure-perl fallback now.
		33
24	=head1 DESCRIPTION	34	=head1 DESCRIPTION
25		35
26	This module converts Perl data structures to JSON and vice versa. Its	36	This module converts Perl data structures to JSON and vice versa. Its
27	primary goal is to be I<correct> and its secondary goal is to be	37	primary goal is to be I<correct> and its secondary goal is to be
28	I<fast>. To reach the latter goal it was written in C.	38	I<fast>. To reach the latter goal it was written in C.
		39
		40	Beginning with version 2.0 of the JSON module, when both JSON and
		41	JSON::XS are installed, then JSON will fall back on JSON::XS (this can be
		42	overridden) with no overhead due to emulation (by inheriting constructor
		43	and methods). If JSON::XS is not available, it will fall back to the
		44	compatible JSON::PP module as backend, so using JSON instead of JSON::XS
		45	gives you a portable JSON API that can be fast when you need and doesn't
		46	require a C compiler when that is a problem.
29		47
30	As this is the n-th-something JSON module on CPAN, what was the reason	48	As this is the n-th-something JSON module on CPAN, what was the reason
31	to write yet another JSON module? While it seems there are many JSON	49	to write yet another JSON module? While it seems there are many JSON
32	modules, none of them correctly handle all corner cases, and in most cases	50	modules, none of them correctly handle all corner cases, and in most cases
33	their maintainers are unresponsive, gone missing, or not listening to bug	51	their maintainers are unresponsive, gone missing, or not listening to bug
…		…
42		60
43	=over 4	61	=over 4
44		62
45	=item * correct Unicode handling	63	=item * correct Unicode handling
46		64
47	This module knows how to handle Unicode, and even documents how and when	65	This module knows how to handle Unicode, documents how and when it does
48	it does so.	66	so, and even documents what "correct" means.
49		67
50	=item * round-trip integrity	68	=item * round-trip integrity
51		69
52	When you serialise a perl data structure using only datatypes supported	70	When you serialise a perl data structure using only data types supported
53	by JSON, the deserialised data structure is identical on the Perl level.	71	by JSON, the deserialised data structure is identical on the Perl level.
54	(e.g. the string "2.0" doesn't suddenly become "2" just because it looks	72	(e.g. the string "2.0" doesn't suddenly become "2" just because it looks
55	like a number).	73	like a number). There minor I<are> exceptions to this, read the MAPPING
		74	section below to learn about those.
56		75
57	=item * strict checking of JSON correctness	76	=item * strict checking of JSON correctness
58		77
59	There is no guessing, no generating of illegal JSON texts by default,	78	There is no guessing, no generating of illegal JSON texts by default,
60	and only JSON is accepted as input by default (the latter is a security	79	and only JSON is accepted as input by default (the latter is a security
61	feature).	80	feature).
62		81
63	=item * fast	82	=item * fast
64		83
65	Compared to other JSON modules, this module compares favourably in terms	84	Compared to other JSON modules and other serialisers such as Storable,
66	of speed, too.	85	this module usually compares favourably in terms of speed, too.
67		86
68	=item * simple to use	87	=item * simple to use
69		88
70	This module has both a simple functional interface as well as an OO	89	This module has both a simple functional interface as well as an object
71	interface.	90	oriented interface interface.
72		91
73	=item * reasonably versatile output formats	92	=item * reasonably versatile output formats
74		93
75	You can choose between the most compact guaranteed single-line format	94	You can choose between the most compact guaranteed-single-line format
76	possible (nice for simple line-based protocols), a pure-ascii format	95	possible (nice for simple line-based protocols), a pure-ASCII format
77	(for when your transport is not 8-bit clean, still supports the whole	96	(for when your transport is not 8-bit clean, still supports the whole
78	Unicode range), or a pretty-printed format (for when you want to read that	97	Unicode range), or a pretty-printed format (for when you want to read that
79	stuff). Or you can combine those features in whatever way you like.	98	stuff). Or you can combine those features in whatever way you like.
80		99
81	=back	100	=back
…		…
84		103
85	package JSON::XS;	104	package JSON::XS;
86		105
87	use strict;	106	use strict;
88		107
89	our $VERSION = '2.0';	108	our $VERSION = '2.222';
90	our @ISA = qw(Exporter);	109	our @ISA = qw(Exporter);
91		110
92	our @EXPORT = qw(to_json from_json);	111	our @EXPORT = qw(encode_json decode_json to_json from_json);
		112
		113	sub to_json($) {
		114	require Carp;
		115	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");
		116	}
		117
		118	sub from_json($) {
		119	require Carp;
		120	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");
		121	}
93		122
94	use Exporter;	123	use Exporter;
95	use XSLoader;	124	use XSLoader;
96		125
97	=head1 FUNCTIONAL INTERFACE	126	=head1 FUNCTIONAL INTERFACE
…		…
99	The following convenience methods are provided by this module. They are	128	The following convenience methods are provided by this module. They are
100	exported by default:	129	exported by default:
101		130
102	=over 4	131	=over 4
103		132
104	=item $json_text = to_json $perl_scalar	133	=item $json_text = encode_json $perl_scalar
105		134
106	Converts the given Perl data structure to a UTF-8 encoded, binary string	135	Converts the given Perl data structure to a UTF-8 encoded, binary string
107	(that is, the string contains octets only). Croaks on error.	136	(that is, the string contains octets only). Croaks on error.
108		137
109	This function call is functionally identical to:	138	This function call is functionally identical to:
110		139
111	$json_text = JSON::XS->new->utf8->encode ($perl_scalar)	140	$json_text = JSON::XS->new->utf8->encode ($perl_scalar)
112		141
113	except being faster.	142	Except being faster.
114		143
115	=item $perl_scalar = from_json $json_text	144	=item $perl_scalar = decode_json $json_text
116		145
117	The opposite of C<to_json>: expects an UTF-8 (binary) string and tries	146	The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries
118	to parse that as an UTF-8 encoded JSON text, returning the resulting	147	to parse that as an UTF-8 encoded JSON text, returning the resulting
119	reference. Croaks on error.	148	reference. Croaks on error.
120		149
121	This function call is functionally identical to:	150	This function call is functionally identical to:
122		151
123	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)	152	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)
124		153
125	except being faster.	154	Except being faster.
126		155
127	=item $is_boolean = JSON::XS::is_bool $scalar	156	=item $is_boolean = JSON::XS::is_bool $scalar
128		157
129	Returns true if the passed scalar represents either JSON::XS::true or	158	Returns true if the passed scalar represents either JSON::XS::true or
130	JSON::XS::false, two constants that act like C<1> and C<0>, respectively	159	JSON::XS::false, two constants that act like C<1> and C<0>, respectively
…		…
148	This enables you to store Unicode characters as single characters in a	177	This enables you to store Unicode characters as single characters in a
149	Perl string - very natural.	178	Perl string - very natural.
150		179
151	=item 2. Perl does I<not> associate an encoding with your strings.	180	=item 2. Perl does I<not> associate an encoding with your strings.
152		181
153	Unless you force it to, e.g. when matching it against a regex, or printing	182	... until you force it to, e.g. when matching it against a regex, or
154	the scalar to a file, in which case Perl either interprets your string as	183	printing the scalar to a file, in which case Perl either interprets your
155	locale-encoded text, octets/binary, or as Unicode, depending on various	184	string as locale-encoded text, octets/binary, or as Unicode, depending
156	settings. In no case is an encoding stored together with your data, it is	185	on various settings. In no case is an encoding stored together with your
157	I<use> that decides encoding, not any magical metadata.	186	data, it is I<use> that decides encoding, not any magical meta data.
158		187
159	=item 3. The internal utf-8 flag has no meaning with regards to the	188	=item 3. The internal utf-8 flag has no meaning with regards to the
160	encoding of your string.	189	encoding of your string.
161		190
162	Just ignore that flag unless you debug a Perl bug, a module written in	191	Just ignore that flag unless you debug a Perl bug, a module written in
…		…
168		197
169	If you didn't know about that flag, just the better, pretend it doesn't	198	If you didn't know about that flag, just the better, pretend it doesn't
170	exist.	199	exist.
171		200
172	=item 4. A "Unicode String" is simply a string where each character can be	201	=item 4. A "Unicode String" is simply a string where each character can be
173	validly interpreted as a Unicode codepoint.	202	validly interpreted as a Unicode code point.
174		203
175	If you have UTF-8 encoded data, it is no longer a Unicode string, but a	204	If you have UTF-8 encoded data, it is no longer a Unicode string, but a
176	Unicode string encoded in UTF-8, giving you a binary string.	205	Unicode string encoded in UTF-8, giving you a binary string.
177		206
178	=item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string.	207	=item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string.
…		…
216		245
217	If C<$enable> is false, then the C<encode> method will not escape Unicode	246	If C<$enable> is false, then the C<encode> method will not escape Unicode
218	characters unless required by the JSON syntax or other flags. This results	247	characters unless required by the JSON syntax or other flags. This results
219	in a faster and more compact format.	248	in a faster and more compact format.
220		249
		250	See also the section I<ENCODING/CODESET FLAG NOTES> later in this
		251	document.
		252
221	The main use for this flag is to produce JSON texts that can be	253	The main use for this flag is to produce JSON texts that can be
222	transmitted over a 7-bit channel, as the encoded JSON texts will not	254	transmitted over a 7-bit channel, as the encoded JSON texts will not
223	contain any 8 bit characters.	255	contain any 8 bit characters.
224		256
225	JSON::XS->new->ascii (1)->encode ([chr 0x10401])	257	JSON::XS->new->ascii (1)->encode ([chr 0x10401])
…		…
236	will not be affected in any way by this flag, as C<decode> by default	268	will not be affected in any way by this flag, as C<decode> by default
237	expects Unicode, which is a strict superset of latin1.	269	expects Unicode, which is a strict superset of latin1.
238		270
239	If C<$enable> is false, then the C<encode> method will not escape Unicode	271	If C<$enable> is false, then the C<encode> method will not escape Unicode
240	characters unless required by the JSON syntax or other flags.	272	characters unless required by the JSON syntax or other flags.
		273
		274	See also the section I<ENCODING/CODESET FLAG NOTES> later in this
		275	document.
241		276
242	The main use for this flag is efficiently encoding binary data as JSON	277	The main use for this flag is efficiently encoding binary data as JSON
243	text, as most octets will not be escaped, resulting in a smaller encoded	278	text, as most octets will not be escaped, resulting in a smaller encoded
244	size. The disadvantage is that the resulting JSON text is encoded	279	size. The disadvantage is that the resulting JSON text is encoded
245	in latin1 (and must correctly be treated as such when storing and	280	in latin1 (and must correctly be treated as such when storing and
…		…
264		299
265	If C<$enable> is false, then the C<encode> method will return the JSON	300	If C<$enable> is false, then the C<encode> method will return the JSON
266	string as a (non-encoded) Unicode string, while C<decode> expects thus a	301	string as a (non-encoded) Unicode string, while C<decode> expects thus a
267	Unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs	302	Unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs
268	to be done yourself, e.g. using the Encode module.	303	to be done yourself, e.g. using the Encode module.
		304
		305	See also the section I<ENCODING/CODESET FLAG NOTES> later in this
		306	document.
269		307
270	Example, output UTF-16BE-encoded JSON:	308	Example, output UTF-16BE-encoded JSON:
271		309
272	use Encode;	310	use Encode;
273	$jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object);	311	$jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object);
…		…
425	resulting in an invalid JSON text:	463	resulting in an invalid JSON text:
426		464
427	JSON::XS->new->allow_nonref->encode ("Hello, World!")	465	JSON::XS->new->allow_nonref->encode ("Hello, World!")
428	=> "Hello, World!"	466	=> "Hello, World!"
429		467
		468	=item $json = $json->allow_unknown ([$enable])
		469
		470	=item $enabled = $json->get_allow_unknown
		471
		472	If C<$enable> is true (or missing), then C<encode> will I<not> throw an
		473	exception when it encounters values it cannot represent in JSON (for
		474	example, filehandles) but instead will encode a JSON C<null> value. Note
		475	that blessed objects are not included here and are handled separately by
		476	c<allow_nonref>.
		477
		478	If C<$enable> is false (the default), then C<encode> will throw an
		479	exception when it encounters anything it cannot encode as JSON.
		480
		481	This option does not affect C<decode> in any way, and it is recommended to
		482	leave it off unless you know your communications partner.
		483
430	=item $json = $json->allow_blessed ([$enable])	484	=item $json = $json->allow_blessed ([$enable])
431		485
432	=item $enabled = $json->get_allow_blessed	486	=item $enabled = $json->get_allow_blessed
433		487
434	If C<$enable> is true (or missing), then the C<encode> method will not	488	If C<$enable> is true (or missing), then the C<encode> method will not
…		…
455	The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON>	509	The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON>
456	returns other blessed objects, those will be handled in the same	510	returns other blessed objects, those will be handled in the same
457	way. C<TO_JSON> must take care of not causing an endless recursion cycle	511	way. C<TO_JSON> must take care of not causing an endless recursion cycle
458	(== crash) in this case. The name of C<TO_JSON> was chosen because other	512	(== crash) in this case. The name of C<TO_JSON> was chosen because other
459	methods called by the Perl core (== not by the user of the object) are	513	methods called by the Perl core (== not by the user of the object) are
460	usually in upper case letters and to avoid collisions with the C<to_json>	514	usually in upper case letters and to avoid collisions with any C<to_json>
461	function.	515	function or method.
462		516
463	This setting does not yet influence C<decode> in any way, but in the	517	This setting does not yet influence C<decode> in any way, but in the
464	future, global hooks might get installed that influence C<decode> and are	518	future, global hooks might get installed that influence C<decode> and are
465	enabled by this setting.	519	enabled by this setting.
466		520
…		…
574	=item $json = $json->max_depth ([$maximum_nesting_depth])	628	=item $json = $json->max_depth ([$maximum_nesting_depth])
575		629
576	=item $max_depth = $json->get_max_depth	630	=item $max_depth = $json->get_max_depth
577		631
578	Sets the maximum nesting level (default C<512>) accepted while encoding	632	Sets the maximum nesting level (default C<512>) accepted while encoding
579	or decoding. If the JSON text or Perl data structure has an equal or	633	or decoding. If a higher nesting level is detected in JSON text or a Perl
580	higher nesting level then this limit, then the encoder and decoder will	634	data structure, then the encoder and decoder will stop and croak at that
581	stop and croak at that point.	635	point.
582		636
583	Nesting level is defined by number of hash- or arrayrefs that the encoder	637	Nesting level is defined by number of hash- or arrayrefs that the encoder
584	needs to traverse to reach a given point or the number of C<{> or C<[>	638	needs to traverse to reach a given point or the number of C<{> or C<[>
585	characters without their matching closing parenthesis crossed to reach a	639	characters without their matching closing parenthesis crossed to reach a
586	given character in a string.	640	given character in a string.
587		641
588	Setting the maximum depth to one disallows any nesting, so that ensures	642	Setting the maximum depth to one disallows any nesting, so that ensures
589	that the object is only a single hash/object or array.	643	that the object is only a single hash/object or array.
590		644
591	The argument to C<max_depth> will be rounded up to the next highest power
592	of two. If no argument is given, the highest possible setting will be	645	If no argument is given, the highest possible setting will be used, which
593	used, which is rarely useful.	646	is rarely useful.
		647
		648	Note that nesting is implemented by recursion in C. The default value has
		649	been chosen to be as large as typical operating systems allow without
		650	crashing.
594		651
595	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.	652	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
596		653
597	=item $json = $json->max_size ([$maximum_string_size])	654	=item $json = $json->max_size ([$maximum_string_size])
598		655
599	=item $max_size = $json->get_max_size	656	=item $max_size = $json->get_max_size
600		657
601	Set the maximum length a JSON text may have (in bytes) where decoding is	658	Set the maximum length a JSON text may have (in bytes) where decoding is
602	being attempted. The default is C<0>, meaning no limit. When C<decode>	659	being attempted. The default is C<0>, meaning no limit. When C<decode>
603	is called on a string longer then this number of characters it will not	660	is called on a string that is longer then this many bytes, it will not
604	attempt to decode the string but throw an exception. This setting has no	661	attempt to decode the string but throw an exception. This setting has no
605	effect on C<encode> (yet).	662	effect on C<encode> (yet).
606		663
607	The argument to C<max_size> will be rounded up to the next B<highest>	664	If no argument is given, the limit check will be deactivated (same as when
608	power of two (so may be more than requested). If no argument is given, the	665	C<0> is specified).
609	limit check will be deactivated (same as when C<0> is specified).
610		666
611	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.	667	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
612		668
613	=item $json_text = $json->encode ($perl_scalar)	669	=item $json_text = $json->encode ($perl_scalar)
614		670
…		…
643	=> ([], 3)	699	=> ([], 3)
644		700
645	=back	701	=back
646		702
647		703
		704	=head1 INCREMENTAL PARSING
		705
		706	In some cases, there is the need for incremental parsing of JSON
		707	texts. While this module always has to keep both JSON text and resulting
		708	Perl data structure in memory at one time, it does allow you to parse a
		709	JSON stream incrementally. It does so by accumulating text until it has
		710	a full JSON object, which it then can decode. This process is similar to
		711	using C<decode_prefix> to see if a full JSON object is available, but
		712	is much more efficient (and can be implemented with a minimum of method
		713	calls).
		714
		715	JSON::XS will only attempt to parse the JSON text once it is sure it
		716	has enough text to get a decisive result, using a very simple but
		717	truly incremental parser. This means that it sometimes won't stop as
		718	early as the full parser, for example, it doesn't detect parenthese
		719	mismatches. The only thing it guarantees is that it starts decoding as
		720	soon as a syntactically valid JSON text has been seen. This means you need
		721	to set resource limits (e.g. C<max_size>) to ensure the parser will stop
		722	parsing in the presence if syntax errors.
		723
		724	The following methods implement this incremental parser.
		725
		726	=over 4
		727
		728	=item [void, scalar or list context] = $json->incr_parse ([$string])
		729
		730	This is the central parsing function. It can both append new text and
		731	extract objects from the stream accumulated so far (both of these
		732	functions are optional).
		733
		734	If C<$string> is given, then this string is appended to the already
		735	existing JSON fragment stored in the C<$json> object.
		736
		737	After that, if the function is called in void context, it will simply
		738	return without doing anything further. This can be used to add more text
		739	in as many chunks as you want.
		740
		741	If the method is called in scalar context, then it will try to extract
		742	exactly I<one> JSON object. If that is successful, it will return this
		743	object, otherwise it will return C<undef>. If there is a parse error,
		744	this method will croak just as C<decode> would do (one can then use
		745	C<incr_skip> to skip the errornous part). This is the most common way of
		746	using the method.
		747
		748	And finally, in list context, it will try to extract as many objects
		749	from the stream as it can find and return them, or the empty list
		750	otherwise. For this to work, there must be no separators between the JSON
		751	objects or arrays, instead they must be concatenated back-to-back. If
		752	an error occurs, an exception will be raised as in the scalar context
		753	case. Note that in this case, any previously-parsed JSON texts will be
		754	lost.
		755
		756	=item $lvalue_string = $json->incr_text
		757
		758	This method returns the currently stored JSON fragment as an lvalue, that
		759	is, you can manipulate it. This I<only> works when a preceding call to
		760	C<incr_parse> in I<scalar context> successfully returned an object. Under
		761	all other circumstances you must not call this function (I mean it.
		762	although in simple tests it might actually work, it I<will> fail under
		763	real world conditions). As a special exception, you can also call this
		764	method before having parsed anything.
		765
		766	This function is useful in two cases: a) finding the trailing text after a
		767	JSON object or b) parsing multiple JSON objects separated by non-JSON text
		768	(such as commas).
		769
		770	=item $json->incr_skip
		771
		772	This will reset the state of the incremental parser and will remove the
		773	parsed text from the input buffer. This is useful after C<incr_parse>
		774	died, in which case the input buffer and incremental parser state is left
		775	unchanged, to skip the text parsed so far and to reset the parse state.
		776
		777	=item $json->incr_reset
		778
		779	This completely resets the incremental parser, that is, after this call,
		780	it will be as if the parser had never parsed anything.
		781
		782	This is useful if you want ot repeatedly parse JSON objects and want to
		783	ignore any trailing data, which means you have to reset the parser after
		784	each successful decode.
		785
		786	=back
		787
		788	=head2 LIMITATIONS
		789
		790	All options that affect decoding are supported, except
		791	C<allow_nonref>. The reason for this is that it cannot be made to
		792	work sensibly: JSON objects and arrays are self-delimited, i.e. you can concatenate
		793	them back to back and still decode them perfectly. This does not hold true
		794	for JSON numbers, however.
		795
		796	For example, is the string C<1> a single JSON number, or is it simply the
		797	start of C<12>? Or is C<12> a single JSON number, or the concatenation
		798	of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS
		799	takes the conservative route and disallows this case.
		800
		801	=head2 EXAMPLES
		802
		803	Some examples will make all this clearer. First, a simple example that
		804	works similarly to C<decode_prefix>: We want to decode the JSON object at
		805	the start of a string and identify the portion after the JSON object:
		806
		807	my $text = "[1,2,3] hello";
		808
		809	my $json = new JSON::XS;
		810
		811	my $obj = $json->incr_parse ($text)
		812	or die "expected JSON object or array at beginning of string";
		813
		814	my $tail = $json->incr_text;
		815	# $tail now contains " hello"
		816
		817	Easy, isn't it?
		818
		819	Now for a more complicated example: Imagine a hypothetical protocol where
		820	you read some requests from a TCP stream, and each request is a JSON
		821	array, without any separation between them (in fact, it is often useful to
		822	use newlines as "separators", as these get interpreted as whitespace at
		823	the start of the JSON text, which makes it possible to test said protocol
		824	with C<telnet>...).
		825
		826	Here is how you'd do it (it is trivial to write this in an event-based
		827	manner):
		828
		829	my $json = new JSON::XS;
		830
		831	# read some data from the socket
		832	while (sysread $socket, my $buf, 4096) {
		833
		834	# split and decode as many requests as possible
		835	for my $request ($json->incr_parse ($buf)) {
		836	# act on the $request
		837	}
		838	}
		839
		840	Another complicated example: Assume you have a string with JSON objects
		841	or arrays, all separated by (optional) comma characters (e.g. C<[1],[2],
		842	[3]>). To parse them, we have to skip the commas between the JSON texts,
		843	and here is where the lvalue-ness of C<incr_text> comes in useful:
		844
		845	my $text = "[1],[2], [3]";
		846	my $json = new JSON::XS;
		847
		848	# void context, so no parsing done
		849	$json->incr_parse ($text);
		850
		851	# now extract as many objects as possible. note the
		852	# use of scalar context so incr_text can be called.
		853	while (my $obj = $json->incr_parse) {
		854	# do something with $obj
		855
		856	# now skip the optional comma
		857	$json->incr_text =~ s/^ \s* , //x;
		858	}
		859
		860	Now lets go for a very complex example: Assume that you have a gigantic
		861	JSON array-of-objects, many gigabytes in size, and you want to parse it,
		862	but you cannot load it into memory fully (this has actually happened in
		863	the real world :).
		864
		865	Well, you lost, you have to implement your own JSON parser. But JSON::XS
		866	can still help you: You implement a (very simple) array parser and let
		867	JSON decode the array elements, which are all full JSON objects on their
		868	own (this wouldn't work if the array elements could be JSON numbers, for
		869	example):
		870
		871	my $json = new JSON::XS;
		872
		873	# open the monster
		874	open my $fh, "<bigfile.json"
		875	or die "bigfile: $!";
		876
		877	# first parse the initial "["
		878	for (;;) {
		879	sysread $fh, my $buf, 65536
		880	or die "read error: $!";
		881	$json->incr_parse ($buf); # void context, so no parsing
		882
		883	# Exit the loop once we found and removed(!) the initial "[".
		884	# In essence, we are (ab-)using the $json object as a simple scalar
		885	# we append data to.
		886	last if $json->incr_text =~ s/^ \s* \[ //x;
		887	}
		888
		889	# now we have the skipped the initial "[", so continue
		890	# parsing all the elements.
		891	for (;;) {
		892	# in this loop we read data until we got a single JSON object
		893	for (;;) {
		894	if (my $obj = $json->incr_parse) {
		895	# do something with $obj
		896	last;
		897	}
		898
		899	# add more data
		900	sysread $fh, my $buf, 65536
		901	or die "read error: $!";
		902	$json->incr_parse ($buf); # void context, so no parsing
		903	}
		904
		905	# in this loop we read data until we either found and parsed the
		906	# separating "," between elements, or the final "]"
		907	for (;;) {
		908	# first skip whitespace
		909	$json->incr_text =~ s/^\s*//;
		910
		911	# if we find "]", we are done
		912	if ($json->incr_text =~ s/^\]//) {
		913	print "finished.\n";
		914	exit;
		915	}
		916
		917	# if we find ",", we can continue with the next element
		918	if ($json->incr_text =~ s/^,//) {
		919	last;
		920	}
		921
		922	# if we find anything else, we have a parse error!
		923	if (length $json->incr_text) {
		924	die "parse error near ", $json->incr_text;
		925	}
		926
		927	# else add more data
		928	sysread $fh, my $buf, 65536
		929	or die "read error: $!";
		930	$json->incr_parse ($buf); # void context, so no parsing
		931	}
		932
		933	This is a complex example, but most of the complexity comes from the fact
		934	that we are trying to be correct (bear with me if I am wrong, I never ran
		935	the above example :).
		936
		937
		938
648	=head1 MAPPING	939	=head1 MAPPING
649		940
650	This section describes how JSON::XS maps Perl values to JSON values and	941	This section describes how JSON::XS maps Perl values to JSON values and
651	vice versa. These mappings are designed to "do the right thing" in most	942	vice versa. These mappings are designed to "do the right thing" in most
652	circumstances automatically, preserving round-tripping characteristics	943	circumstances automatically, preserving round-tripping characteristics
…		…
680		971
681	A JSON number becomes either an integer, numeric (floating point) or	972	A JSON number becomes either an integer, numeric (floating point) or
682	string scalar in perl, depending on its range and any fractional parts. On	973	string scalar in perl, depending on its range and any fractional parts. On
683	the Perl level, there is no difference between those as Perl handles all	974	the Perl level, there is no difference between those as Perl handles all
684	the conversion details, but an integer may take slightly less memory and	975	the conversion details, but an integer may take slightly less memory and
685	might represent more values exactly than (floating point) numbers.	976	might represent more values exactly than floating point numbers.
686		977
687	If the number consists of digits only, JSON::XS will try to represent	978	If the number consists of digits only, JSON::XS will try to represent
688	it as an integer value. If that fails, it will try to represent it as	979	it as an integer value. If that fails, it will try to represent it as
689	a numeric (floating point) value if that is possible without loss of	980	a numeric (floating point) value if that is possible without loss of
690	precision. Otherwise it will preserve the number as a string value.	981	precision. Otherwise it will preserve the number as a string value (in
		982	which case you lose roundtripping ability, as the JSON number will be
		983	re-encoded toa JSON string).
691		984
692	Numbers containing a fractional or exponential part will always be	985	Numbers containing a fractional or exponential part will always be
693	represented as numeric (floating point) values, possibly at a loss of	986	represented as numeric (floating point) values, possibly at a loss of
694	precision.	987	precision (in which case you might lose perfect roundtripping ability, but
695		988	the JSON number will still be re-encoded as a JSON number).
696	This might create round-tripping problems as numbers might become strings,
697	but as Perl is typeless there is no other way to do it.
698		989
699	=item true, false	990	=item true, false
700		991
701	These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>,	992	These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>,
702	respectively. They are overloaded to act almost exactly like the numbers	993	respectively. They are overloaded to act almost exactly like the numbers
…		…
739	Other unblessed references are generally not allowed and will cause an	1030	Other unblessed references are generally not allowed and will cause an
740	exception to be thrown, except for references to the integers C<0> and	1031	exception to be thrown, except for references to the integers C<0> and
741	C<1>, which get turned into C<false> and C<true> atoms in JSON. You can	1032	C<1>, which get turned into C<false> and C<true> atoms in JSON. You can
742	also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability.	1033	also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability.
743		1034
744	to_json [\0,JSON::XS::true] # yields [false,true]	1035	encode_json [\0, JSON::XS::true] # yields [false,true]
745		1036
746	=item JSON::XS::true, JSON::XS::false	1037	=item JSON::XS::true, JSON::XS::false
747		1038
748	These special values become JSON true and JSON false values,	1039	These special values become JSON true and JSON false values,
749	respectively. You can also use C<\1> and C<\0> directly if you want.	1040	respectively. You can also use C<\1> and C<\0> directly if you want.
750		1041
751	=item blessed objects	1042	=item blessed objects
752		1043
753	Blessed objects are not allowed. JSON::XS currently tries to encode their	1044	Blessed objects are not directly representable in JSON. See the
754	underlying representation (hash- or arrayref), but this behaviour might	1045	C<allow_blessed> and C<convert_blessed> methods on various options on
755	change in future versions.	1046	how to deal with this: basically, you can choose between throwing an
		1047	exception, encoding the reference as if it weren't blessed, or provide
		1048	your own serialiser method.
756		1049
757	=item simple scalars	1050	=item simple scalars
758		1051
759	Simple Perl scalars (any scalar that is not a reference) are the most	1052	Simple Perl scalars (any scalar that is not a reference) are the most
760	difficult objects to encode: JSON::XS will encode undefined scalars as	1053	difficult objects to encode: JSON::XS will encode undefined scalars as
761	JSON null value, scalars that have last been used in a string context	1054	JSON C<null> values, scalars that have last been used in a string context
762	before encoding as JSON strings and anything else as number value:	1055	before encoding as JSON strings, and anything else as number value:
763		1056
764	# dump as number	1057	# dump as number
765	to_json [2] # yields [2]	1058	encode_json [2] # yields [2]
766	to_json [-3.0e17] # yields [-3e+17]	1059	encode_json [-3.0e17] # yields [-3e+17]
767	my $value = 5; to_json [$value] # yields [5]	1060	my $value = 5; encode_json [$value] # yields [5]
768		1061
769	# used as string, so dump as string	1062	# used as string, so dump as string
770	print $value;	1063	print $value;
771	to_json [$value] # yields ["5"]	1064	encode_json [$value] # yields ["5"]
772		1065
773	# undef becomes null	1066	# undef becomes null
774	to_json [undef] # yields [null]	1067	encode_json [undef] # yields [null]
775		1068
776	You can force the type to be a JSON string by stringifying it:	1069	You can force the type to be a JSON string by stringifying it:
777		1070
778	my $x = 3.1; # some variable containing a number	1071	my $x = 3.1; # some variable containing a number
779	"$x"; # stringified	1072	"$x"; # stringified
…		…
785	my $x = "3"; # some variable containing a string	1078	my $x = "3"; # some variable containing a string
786	$x += 0; # numify it, ensuring it will be dumped as a number	1079	$x += 0; # numify it, ensuring it will be dumped as a number
787	$x *= 1; # same thing, the choice is yours.	1080	$x *= 1; # same thing, the choice is yours.
788		1081
789	You can not currently force the type in other, less obscure, ways. Tell me	1082	You can not currently force the type in other, less obscure, ways. Tell me
790	if you need this capability.	1083	if you need this capability (but don't forget to explain why it's needed
		1084	:).
791		1085
792	=back	1086	=back
793		1087
794		1088
795	=head1 COMPARISON	1089	=head1 ENCODING/CODESET FLAG NOTES
796		1090
797	As already mentioned, this module was created because none of the existing	1091	The interested reader might have seen a number of flags that signify
798	JSON modules could be made to work correctly. First I will describe the	1092	encodings or codesets - C<utf8>, C<latin1> and C<ascii>. There seems to be
799	problems (or pleasures) I encountered with various existing JSON modules,	1093	some confusion on what these do, so here is a short comparison:
800	followed by some benchmark values. JSON::XS was designed not to suffer	1094
801	from any of these problems or limitations.	1095	C<utf8> controls whether the JSON text created by C<encode> (and expected
		1096	by C<decode>) is UTF-8 encoded or not, while C<latin1> and C<ascii> only
		1097	control whether C<encode> escapes character values outside their respective
		1098	codeset range. Neither of these flags conflict with each other, although
		1099	some combinations make less sense than others.
		1100
		1101	Care has been taken to make all flags symmetrical with respect to
		1102	C<encode> and C<decode>, that is, texts encoded with any combination of
		1103	these flag values will be correctly decoded when the same flags are used
		1104	- in general, if you use different flag settings while encoding vs. when
		1105	decoding you likely have a bug somewhere.
		1106
		1107	Below comes a verbose discussion of these flags. Note that a "codeset" is
		1108	simply an abstract set of character-codepoint pairs, while an encoding
		1109	takes those codepoint numbers and I<encodes> them, in our case into
		1110	octets. Unicode is (among other things) a codeset, UTF-8 is an encoding,
		1111	and ISO-8859-1 (= latin 1) and ASCII are both codesets I<and> encodings at
		1112	the same time, which can be confusing.
802		1113
803	=over 4	1114	=over 4
804		1115
805	=item JSON 1.07	1116	=item C<utf8> flag disabled
806		1117
807	Slow (but very portable, as it is written in pure Perl).	1118	When C<utf8> is disabled (the default), then C<encode>/C<decode> generate
		1119	and expect Unicode strings, that is, characters with high ordinal Unicode
		1120	values (> 255) will be encoded as such characters, and likewise such
		1121	characters are decoded as-is, no canges to them will be done, except
		1122	"(re-)interpreting" them as Unicode codepoints or Unicode characters,
		1123	respectively (to Perl, these are the same thing in strings unless you do
		1124	funny/weird/dumb stuff).
808		1125
809	Undocumented/buggy Unicode handling (how JSON handles Unicode values is	1126	This is useful when you want to do the encoding yourself (e.g. when you
810	undocumented. One can get far by feeding it Unicode strings and doing	1127	want to have UTF-16 encoded JSON texts) or when some other layer does
811	en-/decoding oneself, but Unicode escapes are not working properly).	1128	the encoding for you (for example, when printing to a terminal using a
		1129	filehandle that transparently encodes to UTF-8 you certainly do NOT want
		1130	to UTF-8 encode your data first and have Perl encode it another time).
812		1131
813	No round-tripping (strings get clobbered if they look like numbers, e.g.	1132	=item C<utf8> flag enabled
814	the string C<2.0> will encode to C<2.0> instead of C<"2.0">, and that will
815	decode into the number 2.
816		1133
817	=item JSON::PC 0.01	1134	If the C<utf8>-flag is enabled, C<encode>/C<decode> will encode all
		1135	characters using the corresponding UTF-8 multi-byte sequence, and will
		1136	expect your input strings to be encoded as UTF-8, that is, no "character"
		1137	of the input string must have any value > 255, as UTF-8 does not allow
		1138	that.
818		1139
819	Very fast.	1140	The C<utf8> flag therefore switches between two modes: disabled means you
		1141	will get a Unicode string in Perl, enabled means you get an UTF-8 encoded
		1142	octet/binary string in Perl.
820		1143
821	Undocumented/buggy Unicode handling.	1144	=item C<latin1> or C<ascii> flags enabled
822		1145
823	No round-tripping.	1146	With C<latin1> (or C<ascii>) enabled, C<encode> will escape characters
		1147	with ordinal values > 255 (> 127 with C<ascii>) and encode the remaining
		1148	characters as specified by the C<utf8> flag.
824		1149
825	Has problems handling many Perl values (e.g. regex results and other magic	1150	If C<utf8> is disabled, then the result is also correctly encoded in those
826	values will make it croak).	1151	character sets (as both are proper subsets of Unicode, meaning that a
		1152	Unicode string with all character values < 256 is the same thing as a
		1153	ISO-8859-1 string, and a Unicode string with all character values < 128 is
		1154	the same thing as an ASCII string in Perl).
827		1155
828	Does not even generate valid JSON (C<{1,2}> gets converted to C<{1:2}>	1156	If C<utf8> is enabled, you still get a correct UTF-8-encoded string,
829	which is not a valid JSON text.	1157	regardless of these flags, just some more characters will be escaped using
		1158	C<\uXXXX> then before.
830		1159
831	Unmaintained (maintainer unresponsive for many months, bugs are not	1160	Note that ISO-8859-1-I<encoded> strings are not compatible with UTF-8
832	getting fixed).	1161	encoding, while ASCII-encoded strings are. That is because the ISO-8859-1
		1162	encoding is NOT a subset of UTF-8 (despite the ISO-8859-1 I<codeset> being
		1163	a subset of Unicode), while ASCII is.
833		1164
834	=item JSON::Syck 0.21	1165	Surprisingly, C<decode> will ignore these flags and so treat all input
		1166	values as governed by the C<utf8> flag. If it is disabled, this allows you
		1167	to decode ISO-8859-1- and ASCII-encoded strings, as both strict subsets of
		1168	Unicode. If it is enabled, you can correctly decode UTF-8 encoded strings.
835		1169
836	Very buggy (often crashes).	1170	So neither C<latin1> nor C<ascii> are incompatible with the C<utf8> flag -
		1171	they only govern when the JSON output engine escapes a character or not.
837		1172
838	Very inflexible (no human-readable format supported, format pretty much	1173	The main use for C<latin1> is to relatively efficiently store binary data
839	undocumented. I need at least a format for easy reading by humans and a	1174	as JSON, at the expense of breaking compatibility with most JSON decoders.
840	single-line compact format for use in a protocol, and preferably a way to
841	generate ASCII-only JSON texts).
842		1175
843	Completely broken (and confusingly documented) Unicode handling (Unicode	1176	The main use for C<ascii> is to force the output to not contain characters
844	escapes are not working properly, you need to set ImplicitUnicode to	1177	with values > 127, which means you can interpret the resulting string
845	I<different> values on en- and decoding to get symmetric behaviour).	1178	as UTF-8, ISO-8859-1, ASCII, KOI8-R or most about any character set and
846		1179	8-bit-encoding, and still get the same data structure back. This is useful
847	No round-tripping (simple cases work, but this depends on whether the scalar	1180	when your channel for JSON transfer is not 8-bit clean or the encoding
848	value was used in a numeric context or not).	1181	might be mangled in between (e.g. in mail), and works because ASCII is a
849		1182	proper subset of most 8-bit and multibyte encodings in use in the world.
850	Dumping hashes may skip hash values depending on iterator state.
851
852	Unmaintained (maintainer unresponsive for many months, bugs are not
853	getting fixed).
854
855	Does not check input for validity (i.e. will accept non-JSON input and
856	return "something" instead of raising an exception. This is a security
857	issue: imagine two banks transferring money between each other using
858	JSON. One bank might parse a given non-JSON request and deduct money,
859	while the other might reject the transaction with a syntax error. While a
860	good protocol will at least recover, that is extra unnecessary work and
861	the transaction will still not succeed).
862
863	=item JSON::DWIW 0.04
864
865	Very fast. Very natural. Very nice.
866
867	Undocumented Unicode handling (but the best of the pack. Unicode escapes
868	still don't get parsed properly).
869
870	Very inflexible.
871
872	No round-tripping.
873
874	Does not generate valid JSON texts (key strings are often unquoted, empty keys
875	result in nothing being output)
876
877	Does not check input for validity.
878		1183
879	=back	1184	=back
880		1185
881		1186
882	=head2 JSON and YAML	1187	=head2 JSON and YAML
883		1188
884	You often hear that JSON is a subset (or a close subset) of YAML. This is,	1189	You often hear that JSON is a subset of YAML. This is, however, a mass
885	however, a mass hysteria and very far from the truth. In general, there is	1190	hysteria(*) and very far from the truth (as of the time of this writing),
886	no way to configure JSON::XS to output a data structure as valid YAML.	1191	so let me state it clearly: I<in general, there is no way to configure
		1192	JSON::XS to output a data structure as valid YAML> that works in all
		1193	cases.
887		1194
888	If you really must use JSON::XS to generate YAML, you should use this	1195	If you really must use JSON::XS to generate YAML, you should use this
889	algorithm (subject to change in future versions):	1196	algorithm (subject to change in future versions):
890		1197
891	my $to_yaml = JSON::XS->new->utf8->space_after (1);	1198	my $to_yaml = JSON::XS->new->utf8->space_after (1);
892	my $yaml = $to_yaml->encode ($ref) . "\n";	1199	my $yaml = $to_yaml->encode ($ref) . "\n";
893		1200
894	This will usually generate JSON texts that also parse as valid	1201	This will I<usually> generate JSON texts that also parse as valid
895	YAML. Please note that YAML has hardcoded limits on (simple) object key	1202	YAML. Please note that YAML has hardcoded limits on (simple) object key
896	lengths that JSON doesn't have, so you should make sure that your hash	1203	lengths that JSON doesn't have and also has different and incompatible
		1204	unicode handling, so you should make sure that your hash keys are
897	keys are noticeably shorter than the 1024 characters YAML allows.	1205	noticeably shorter than the 1024 "stream characters" YAML allows and that
		1206	you do not have characters with codepoint values outside the Unicode BMP
		1207	(basic multilingual page). YAML also does not allow C<\/> sequences in
		1208	strings (which JSON::XS does not I<currently> generate, but other JSON
		1209	generators might).
898		1210
899	There might be other incompatibilities that I am not aware of. In general	1211	There might be other incompatibilities that I am not aware of (or the YAML
		1212	specification has been changed yet again - it does so quite often). In
900	you should not try to generate YAML with a JSON generator or vice versa,	1213	general you should not try to generate YAML with a JSON generator or vice
901	or try to parse JSON with a YAML parser or vice versa: chances are high	1214	versa, or try to parse JSON with a YAML parser or vice versa: chances are
902	that you will run into severe interoperability problems.	1215	high that you will run into severe interoperability problems when you
		1216	least expect it.
		1217
		1218	=over 4
		1219
		1220	=item (*)
		1221
		1222	I have been pressured multiple times by Brian Ingerson (one of the
		1223	authors of the YAML specification) to remove this paragraph, despite him
		1224	acknowledging that the actual incompatibilities exist. As I was personally
		1225	bitten by this "JSON is YAML" lie, I refused and said I will continue to
		1226	educate people about these issues, so others do not run into the same
		1227	problem again and again. After this, Brian called me a (quote)I<complete
		1228	and worthless idiot>(unquote).
		1229
		1230	In my opinion, instead of pressuring and insulting people who actually
		1231	clarify issues with YAML and the wrong statements of some of its
		1232	proponents, I would kindly suggest reading the JSON spec (which is not
		1233	that difficult or long) and finally make YAML compatible to it, and
		1234	educating users about the changes, instead of spreading lies about the
		1235	real compatibility for many I<years> and trying to silence people who
		1236	point out that it isn't true.
		1237
		1238	=back
903		1239
904		1240
905	=head2 SPEED	1241	=head2 SPEED
906		1242
907	It seems that JSON::XS is surprisingly fast, as shown in the following	1243	It seems that JSON::XS is surprisingly fast, as shown in the following
908	tables. They have been generated with the help of the C<eg/bench> program	1244	tables. They have been generated with the help of the C<eg/bench> program
909	in the JSON::XS distribution, to make it easy to compare on your own	1245	in the JSON::XS distribution, to make it easy to compare on your own
910	system.	1246	system.
911		1247
912	First comes a comparison between various modules using a very short	1248	First comes a comparison between various modules using
913	single-line JSON string:	1249	a very short single-line JSON string (also available at
		1250	L<http://dist.schmorp.de/misc/json/short.json>).
914		1251
915	{"method": "handleMessage", "params": ["user1", "we were just talking"], \	1252	{"method": "handleMessage", "params": ["user1",
916	"id": null, "array":[1,11,234,-5,1e5,1e7, true, false]}	1253	"we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7,
		1254	true, false]}
917		1255
918	It shows the number of encodes/decodes per second (JSON::XS uses	1256	It shows the number of encodes/decodes per second (JSON::XS uses
919	the functional interface, while JSON::XS/2 uses the OO interface	1257	the functional interface, while JSON::XS/2 uses the OO interface
920	with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables	1258	with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables
921	shrink). Higher is better:	1259	shrink). Higher is better:
…		…
937	about three times faster on decoding, and over forty times faster	1275	about three times faster on decoding, and over forty times faster
938	than JSON, even with pretty-printing and key sorting. It also compares	1276	than JSON, even with pretty-printing and key sorting. It also compares
939	favourably to Storable for small amounts of data.	1277	favourably to Storable for small amounts of data.
940		1278
941	Using a longer test string (roughly 18KB, generated from Yahoo! Locals	1279	Using a longer test string (roughly 18KB, generated from Yahoo! Locals
942	search API (http://nanoref.com/yahooapis/mgPdGg):	1280	search API (L<http://dist.schmorp.de/misc/json/long.json>).
943		1281
944	module \| encode \| decode \|	1282	module \| encode \| decode \|
945	-----------\|------------\|------------\|	1283	-----------\|------------\|------------\|
946	JSON 1.x \| 55.260 \| 34.971 \|	1284	JSON 1.x \| 55.260 \| 34.971 \|
947	JSON::DWIW \| 825.228 \| 1082.513 \|	1285	JSON::DWIW \| 825.228 \| 1082.513 \|
…		…
984		1322
985	Third, JSON::XS recurses using the C stack when decoding objects and	1323	Third, JSON::XS recurses using the C stack when decoding objects and
986	arrays. The C stack is a limited resource: for instance, on my amd64	1324	arrays. The C stack is a limited resource: for instance, on my amd64
987	machine with 8MB of stack size I can decode around 180k nested arrays but	1325	machine with 8MB of stack size I can decode around 180k nested arrays but
988	only 14k nested JSON objects (due to perl itself recursing deeply on croak	1326	only 14k nested JSON objects (due to perl itself recursing deeply on croak
989	to free the temporary). If that is exceeded, the program crashes. to be	1327	to free the temporary). If that is exceeded, the program crashes. To be
990	conservative, the default nesting limit is set to 512. If your process	1328	conservative, the default nesting limit is set to 512. If your process
991	has a smaller stack, you should adjust this setting accordingly with the	1329	has a smaller stack, you should adjust this setting accordingly with the
992	C<max_depth> method.	1330	C<max_depth> method.
993		1331
994	And last but least, something else could bomb you that I forgot to think	1332	Something else could bomb you, too, that I forgot to think of. In that
995	of. In that case, you get to keep the pieces. I am always open for hints,	1333	case, you get to keep the pieces. I am always open for hints, though...
996	though...	1334
		1335	Also keep in mind that JSON::XS might leak contents of your Perl data
		1336	structures in its error messages, so when you serialise sensitive
		1337	information you might want to make sure that exceptions thrown by JSON::XS
		1338	will not end up in front of untrusted eyes.
997		1339
998	If you are using JSON::XS to return packets to consumption	1340	If you are using JSON::XS to return packets to consumption
999	by JavaScript scripts in a browser you should have a look at	1341	by JavaScript scripts in a browser you should have a look at
1000	L<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether	1342	L<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether
1001	you are vulnerable to some common attack vectors (which really are browser	1343	you are vulnerable to some common attack vectors (which really are browser
1002	design bugs, but it is still you who will have to deal with it, as major	1344	design bugs, but it is still you who will have to deal with it, as major
1003	browser developers care only for features, not about doing security	1345	browser developers care only for features, not about getting security
1004	right).	1346	right).
1005		1347
1006		1348
1007	=head1 THREADS	1349	=head1 THREADS
1008		1350
1009	This module is I<not> guaranteed to be thread safe and there are no	1351	This module is I<not> guaranteed to be thread safe and there are no
1010	plans to change this until Perl gets thread support (as opposed to the	1352	plans to change this until Perl gets thread support (as opposed to the
1011	horribly slow so-called "threads" which are simply slow and bloated	1353	horribly slow so-called "threads" which are simply slow and bloated
1012	process simulations - use fork, its I<much> faster, cheaper, better).	1354	process simulations - use fork, it's I<much> faster, cheaper, better).
1013		1355
1014	(It might actually work, but you have been warned).	1356	(It might actually work, but you have been warned).
1015		1357
1016		1358
1017	=head1 BUGS	1359	=head1 BUGS
1018		1360
1019	While the goal of this module is to be correct, that unfortunately does	1361	While the goal of this module is to be correct, that unfortunately does
1020	not mean its bug-free, only that I think its design is bug-free. It is	1362	not mean it's bug-free, only that I think its design is bug-free. If you
1021	still relatively early in its development. If you keep reporting bugs they	1363	keep reporting bugs they will be fixed swiftly, though.
1022	will be fixed swiftly, though.
1023		1364
1024	Please refrain from using rt.cpan.org or any other bug reporting	1365	Please refrain from using rt.cpan.org or any other bug reporting
1025	service. I put the contact address into my modules for a reason.	1366	service. I put the contact address into my modules for a reason.
1026		1367
1027	=cut	1368	=cut
…		…
1047	"--" => sub { $_[0] = ${$_[0]} - 1 },	1388	"--" => sub { $_[0] = ${$_[0]} - 1 },
1048	fallback => 1;	1389	fallback => 1;
1049		1390
1050	1;	1391	1;
1051		1392
		1393	=head1 SEE ALSO
		1394
		1395	The F<json_xs> command line utility for quick experiments.
		1396
1052	=head1 AUTHOR	1397	=head1 AUTHOR
1053		1398
1054	Marc Lehmann <schmorp@schmorp.de>	1399	Marc Lehmann <schmorp@schmorp.de>
1055	http://home.schmorp.de/	1400	http://home.schmorp.de/
1056		1401

Diff Legend

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

Comparing JSON-XS/XS.pm (file contents): Revision 1.76 by root, Sun Dec 2 15:34:13 2007 UTC vs. Revision 1.109 by root, Sat Jul 19 04:21:32 2008 UTC

Diff Legend

Comparing JSON-XS/XS.pm (file contents):
Revision 1.76 by root, Sun Dec 2 15:34:13 2007 UTC vs.
Revision 1.109 by root, Sat Jul 19 04:21:32 2008 UTC