[ViewVC] Diff of: cvs/JSON-XS/README

Comparing JSON-XS/README (file contents):
Revision 1.20 by root, Tue Nov 13 22:59:08 2007 UTC vs.
Revision 1.29 by root, Thu Feb 19 01:13:46 2009 UTC

…		…
1	NAME	1	NAME
2	JSON::XS - JSON serialising/deserialising, done correctly and fast	2	JSON::XS - JSON serialising/deserialising, done correctly and fast
3		3
4	JSON::XS - 正しくて高速な JSON	4	JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ
5	シリアライザ/デシリアライザ
6	(http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html)	5	(http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html)
7		6
8	SYNOPSIS	7	SYNOPSIS
9	use JSON::XS;	8	use JSON::XS;
10		9
11	# exported functions, they croak on error	10	# exported functions, they croak on error
12	# and expect/generate UTF-8	11	# and expect/generate UTF-8
13		12
14	$utf8_encoded_json_text = to_json $perl_hash_or_arrayref;	13	$utf8_encoded_json_text = encode_json $perl_hash_or_arrayref;
15	$perl_hash_or_arrayref = from_json $utf8_encoded_json_text;	14	$perl_hash_or_arrayref = decode_json $utf8_encoded_json_text;
16		15
17	# OO-interface	16	# OO-interface
18		17
19	$coder = JSON::XS->new->ascii->pretty->allow_nonref;	18	$coder = JSON::XS->new->ascii->pretty->allow_nonref;
20	$pretty_printed_unencoded = $coder->encode ($perl_scalar);	19	$pretty_printed_unencoded = $coder->encode ($perl_scalar);
21	$perl_scalar = $coder->decode ($unicode_json_text);	20	$perl_scalar = $coder->decode ($unicode_json_text);
		21
		22	# Note that JSON version 2.0 and above will automatically use JSON::XS
		23	# if available, at virtually no speed overhead either, so you should
		24	# be able to just:
		25
		26	use JSON;
		27
		28	# and do the same things, except that you have a pure-perl fallback now.
22		29
23	DESCRIPTION	30	DESCRIPTION
24	This module converts Perl data structures to JSON and vice versa. Its	31	This module converts Perl data structures to JSON and vice versa. Its
25	primary goal is to be correct and its secondary goal is to be fast.	32	primary goal is to be correct and its secondary goal is to be fast.
26	To reach the latter goal it was written in C.	33	To reach the latter goal it was written in C.
		34
		35	Beginning with version 2.0 of the JSON module, when both JSON and
		36	JSON::XS are installed, then JSON will fall back on JSON::XS (this can
		37	be overridden) with no overhead due to emulation (by inheriting
		38	constructor and methods). If JSON::XS is not available, it will fall
		39	back to the compatible JSON::PP module as backend, so using JSON instead
		40	of JSON::XS gives you a portable JSON API that can be fast when you need
		41	and doesn't require a C compiler when that is a problem.
27		42
28	As this is the n-th-something JSON module on CPAN, what was the reason	43	As this is the n-th-something JSON module on CPAN, what was the reason
29	to write yet another JSON module? While it seems there are many JSON	44	to write yet another JSON module? While it seems there are many JSON
30	modules, none of them correctly handle all corner cases, and in most	45	modules, none of them correctly handle all corner cases, and in most
31	cases their maintainers are unresponsive, gone missing, or not listening	46	cases their maintainers are unresponsive, gone missing, or not listening
32	to bug reports for other reasons.	47	to bug reports for other reasons.
33		48
34	See COMPARISON, below, for a comparison to some other JSON modules.
35
36	See MAPPING, below, on how JSON::XS maps perl values to JSON values and	49	See MAPPING, below, on how JSON::XS maps perl values to JSON values and
37	vice versa.	50	vice versa.
38		51
39	FEATURES	52	FEATURES
40	* correct Unicode handling	53	* correct Unicode handling
		54
41	This module knows how to handle Unicode, and even documents how and	55	This module knows how to handle Unicode, documents how and when it
42	when it does so.	56	does so, and even documents what "correct" means.
43		57
44	* round-trip integrity	58	* round-trip integrity
		59
45	When you serialise a perl data structure using only datatypes	60	When you serialise a perl data structure using only data types
46	supported by JSON, the deserialised data structure is identical on	61	supported by JSON, the deserialised data structure is identical on
47	the Perl level. (e.g. the string "2.0" doesn't suddenly become "2"	62	the Perl level. (e.g. the string "2.0" doesn't suddenly become "2"
48	just because it looks like a number).	63	just because it looks like a number). There minor are exceptions
		64	to this, read the MAPPING section below to learn about those.
49		65
50	* strict checking of JSON correctness	66	* strict checking of JSON correctness
		67
51	There is no guessing, no generating of illegal JSON texts by	68	There is no guessing, no generating of illegal JSON texts by
52	default, and only JSON is accepted as input by default (the latter	69	default, and only JSON is accepted as input by default (the latter
53	is a security feature).	70	is a security feature).
54		71
55	* fast	72	* fast
56	Compared to other JSON modules, this module compares favourably in
57	terms of speed, too.
58		73
		74	Compared to other JSON modules and other serialisers such as
		75	Storable, this module usually compares favourably in terms of speed,
		76	too.
		77
59	* simple to use	78	* simple to use
		79
60	This module has both a simple functional interface as well as an OO	80	This module has both a simple functional interface as well as an
61	interface.	81	object oriented interface interface.
62		82
63	* reasonably versatile output formats	83	* reasonably versatile output formats
		84
64	You can choose between the most compact guaranteed single-line	85	You can choose between the most compact guaranteed-single-line
65	format possible (nice for simple line-based protocols), a pure-ascii	86	format possible (nice for simple line-based protocols), a pure-ASCII
66	format (for when your transport is not 8-bit clean, still supports	87	format (for when your transport is not 8-bit clean, still supports
67	the whole Unicode range), or a pretty-printed format (for when you	88	the whole Unicode range), or a pretty-printed format (for when you
68	want to read that stuff). Or you can combine those features in	89	want to read that stuff). Or you can combine those features in
69	whatever way you like.	90	whatever way you like.
70		91
71	FUNCTIONAL INTERFACE	92	FUNCTIONAL INTERFACE
72	The following convenience methods are provided by this module. They are	93	The following convenience methods are provided by this module. They are
73	exported by default:	94	exported by default:
74		95
75	$json_text = to_json $perl_scalar	96	$json_text = encode_json $perl_scalar
76	Converts the given Perl data structure to a UTF-8 encoded, binary	97	Converts the given Perl data structure to a UTF-8 encoded, binary
77	string (that is, the string contains octets only). Croaks on error.	98	string (that is, the string contains octets only). Croaks on error.
78		99
79	This function call is functionally identical to:	100	This function call is functionally identical to:
80		101
81	$json_text = JSON::XS->new->utf8->encode ($perl_scalar)	102	$json_text = JSON::XS->new->utf8->encode ($perl_scalar)
82		103
83	except being faster.	104	Except being faster.
84		105
85	$perl_scalar = from_json $json_text	106	$perl_scalar = decode_json $json_text
86	The opposite of "to_json": expects an UTF-8 (binary) string and	107	The opposite of "encode_json": expects an UTF-8 (binary) string and
87	tries to parse that as an UTF-8 encoded JSON text, returning the	108	tries to parse that as an UTF-8 encoded JSON text, returning the
88	resulting reference. Croaks on error.	109	resulting reference. Croaks on error.
89		110
90	This function call is functionally identical to:	111	This function call is functionally identical to:
91		112
92	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)	113	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)
93		114
94	except being faster.	115	Except being faster.
95		116
96	$is_boolean = JSON::XS::is_bool $scalar	117	$is_boolean = JSON::XS::is_bool $scalar
97	Returns true if the passed scalar represents either JSON::XS::true	118	Returns true if the passed scalar represents either JSON::XS::true
98	or JSON::XS::false, two constants that act like 1 and 0,	119	or JSON::XS::false, two constants that act like 1 and 0,
99	respectively and are used to represent JSON "true" and "false"	120	respectively and are used to represent JSON "true" and "false"
109	1. Perl strings can store characters with ordinal values > 255.	130	1. Perl strings can store characters with ordinal values > 255.
110	This enables you to store Unicode characters as single characters in	131	This enables you to store Unicode characters as single characters in
111	a Perl string - very natural.	132	a Perl string - very natural.
112		133
113	2. Perl does not associate an encoding with your strings.	134	2. Perl does not associate an encoding with your strings.
114	Unless you force it to, e.g. when matching it against a regex, or	135	... until you force it to, e.g. when matching it against a regex, or
115	printing the scalar to a file, in which case Perl either interprets	136	printing the scalar to a file, in which case Perl either interprets
116	your string as locale-encoded text, octets/binary, or as Unicode,	137	your string as locale-encoded text, octets/binary, or as Unicode,
117	depending on various settings. In no case is an encoding stored	138	depending on various settings. In no case is an encoding stored
118	together with your data, it is use that decides encoding, not any	139	together with your data, it is use that decides encoding, not any
119	magical metadata.	140	magical meta data.
120		141
121	3. The internal utf-8 flag has no meaning with regards to the encoding	142	3. The internal utf-8 flag has no meaning with regards to the encoding
122	of your string.	143	of your string.
123	Just ignore that flag unless you debug a Perl bug, a module written	144	Just ignore that flag unless you debug a Perl bug, a module written
124	in XS or want to dive into the internals of perl. Otherwise it will	145	in XS or want to dive into the internals of perl. Otherwise it will
…		…
129		150
130	If you didn't know about that flag, just the better, pretend it	151	If you didn't know about that flag, just the better, pretend it
131	doesn't exist.	152	doesn't exist.
132		153
133	4. A "Unicode String" is simply a string where each character can be	154	4. A "Unicode String" is simply a string where each character can be
134	validly interpreted as a Unicode codepoint.	155	validly interpreted as a Unicode code point.
135	If you have UTF-8 encoded data, it is no longer a Unicode string,	156	If you have UTF-8 encoded data, it is no longer a Unicode string,
136	but a Unicode string encoded in UTF-8, giving you a binary string.	157	but a Unicode string encoded in UTF-8, giving you a binary string.
137		158
138	5. A string containing "high" (> 255) character values is not a UTF-8	159	5. A string containing "high" (> 255) character values is not a UTF-8
139	string.	160	string.
…		…
155		176
156	my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]})	177	my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]})
157	=> {"a": [1, 2]}	178	=> {"a": [1, 2]}
158		179
159	$json = $json->ascii ([$enable])	180	$json = $json->ascii ([$enable])
		181	$enabled = $json->get_ascii
160	If $enable is true (or missing), then the "encode" method will not	182	If $enable is true (or missing), then the "encode" method will not
161	generate characters outside the code range 0..127 (which is ASCII).	183	generate characters outside the code range 0..127 (which is ASCII).
162	Any Unicode characters outside that range will be escaped using	184	Any Unicode characters outside that range will be escaped using
163	either a single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL	185	either a single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL
164	escape sequence, as per RFC4627. The resulting encoded JSON text can	186	escape sequence, as per RFC4627. The resulting encoded JSON text can
…		…
168		190
169	If $enable is false, then the "encode" method will not escape	191	If $enable is false, then the "encode" method will not escape
170	Unicode characters unless required by the JSON syntax or other	192	Unicode characters unless required by the JSON syntax or other
171	flags. This results in a faster and more compact format.	193	flags. This results in a faster and more compact format.
172		194
		195	See also the section ENCODING/CODESET FLAG NOTES later in this
		196	document.
		197
173	The main use for this flag is to produce JSON texts that can be	198	The main use for this flag is to produce JSON texts that can be
174	transmitted over a 7-bit channel, as the encoded JSON texts will not	199	transmitted over a 7-bit channel, as the encoded JSON texts will not
175	contain any 8 bit characters.	200	contain any 8 bit characters.
176		201
177	JSON::XS->new->ascii (1)->encode ([chr 0x10401])	202	JSON::XS->new->ascii (1)->encode ([chr 0x10401])
178	=> ["\ud801\udc01"]	203	=> ["\ud801\udc01"]
179		204
180	$json = $json->latin1 ([$enable])	205	$json = $json->latin1 ([$enable])
		206	$enabled = $json->get_latin1
181	If $enable is true (or missing), then the "encode" method will	207	If $enable is true (or missing), then the "encode" method will
182	encode the resulting JSON text as latin1 (or iso-8859-1), escaping	208	encode the resulting JSON text as latin1 (or iso-8859-1), escaping
183	any characters outside the code range 0..255. The resulting string	209	any characters outside the code range 0..255. The resulting string
184	can be treated as a latin1-encoded JSON text or a native Unicode	210	can be treated as a latin1-encoded JSON text or a native Unicode
185	string. The "decode" method will not be affected in any way by this	211	string. The "decode" method will not be affected in any way by this
…		…
187	superset of latin1.	213	superset of latin1.
188		214
189	If $enable is false, then the "encode" method will not escape	215	If $enable is false, then the "encode" method will not escape
190	Unicode characters unless required by the JSON syntax or other	216	Unicode characters unless required by the JSON syntax or other
191	flags.	217	flags.
		218
		219	See also the section ENCODING/CODESET FLAG NOTES later in this
		220	document.
192		221
193	The main use for this flag is efficiently encoding binary data as	222	The main use for this flag is efficiently encoding binary data as
194	JSON text, as most octets will not be escaped, resulting in a	223	JSON text, as most octets will not be escaped, resulting in a
195	smaller encoded size. The disadvantage is that the resulting JSON	224	smaller encoded size. The disadvantage is that the resulting JSON
196	text is encoded in latin1 (and must correctly be treated as such	225	text is encoded in latin1 (and must correctly be treated as such
…		…
201		230
202	JSON::XS->new->latin1->encode (["\x{89}\x{abc}"]	231	JSON::XS->new->latin1->encode (["\x{89}\x{abc}"]
203	=> ["\x{89}\\u0abc"] # (perl syntax, U+abc escaped, U+89 not)	232	=> ["\x{89}\\u0abc"] # (perl syntax, U+abc escaped, U+89 not)
204		233
205	$json = $json->utf8 ([$enable])	234	$json = $json->utf8 ([$enable])
		235	$enabled = $json->get_utf8
206	If $enable is true (or missing), then the "encode" method will	236	If $enable is true (or missing), then the "encode" method will
207	encode the JSON result into UTF-8, as required by many protocols,	237	encode the JSON result into UTF-8, as required by many protocols,
208	while the "decode" method expects to be handled an UTF-8-encoded	238	while the "decode" method expects to be handled an UTF-8-encoded
209	string. Please note that UTF-8-encoded strings do not contain any	239	string. Please note that UTF-8-encoded strings do not contain any
210	characters outside the range 0..255, they are thus useful for	240	characters outside the range 0..255, they are thus useful for
…		…
215	If $enable is false, then the "encode" method will return the JSON	245	If $enable is false, then the "encode" method will return the JSON
216	string as a (non-encoded) Unicode string, while "decode" expects	246	string as a (non-encoded) Unicode string, while "decode" expects
217	thus a Unicode string. Any decoding or encoding (e.g. to UTF-8 or	247	thus a Unicode string. Any decoding or encoding (e.g. to UTF-8 or
218	UTF-16) needs to be done yourself, e.g. using the Encode module.	248	UTF-16) needs to be done yourself, e.g. using the Encode module.
219		249
		250	See also the section ENCODING/CODESET FLAG NOTES later in this
		251	document.
		252
220	Example, output UTF-16BE-encoded JSON:	253	Example, output UTF-16BE-encoded JSON:
221		254
222	use Encode;	255	use Encode;
223	$jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object);	256	$jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object);
224		257
…		…
242	2	275	2
243	]	276	]
244	}	277	}
245		278
246	$json = $json->indent ([$enable])	279	$json = $json->indent ([$enable])
		280	$enabled = $json->get_indent
247	If $enable is true (or missing), then the "encode" method will use a	281	If $enable is true (or missing), then the "encode" method will use a
248	multiline format as output, putting every array member or	282	multiline format as output, putting every array member or
249	object/hash key-value pair into its own line, indenting them	283	object/hash key-value pair into its own line, indenting them
250	properly.	284	properly.
251		285
…		…
253	the resulting JSON text is guaranteed not to contain any "newlines".	287	the resulting JSON text is guaranteed not to contain any "newlines".
254		288
255	This setting has no effect when decoding JSON texts.	289	This setting has no effect when decoding JSON texts.
256		290
257	$json = $json->space_before ([$enable])	291	$json = $json->space_before ([$enable])
		292	$enabled = $json->get_space_before
258	If $enable is true (or missing), then the "encode" method will add	293	If $enable is true (or missing), then the "encode" method will add
259	an extra optional space before the ":" separating keys from values	294	an extra optional space before the ":" separating keys from values
260	in JSON objects.	295	in JSON objects.
261		296
262	If $enable is false, then the "encode" method will not add any extra	297	If $enable is false, then the "encode" method will not add any extra
…		…
268	Example, space_before enabled, space_after and indent disabled:	303	Example, space_before enabled, space_after and indent disabled:
269		304
270	{"key" :"value"}	305	{"key" :"value"}
271		306
272	$json = $json->space_after ([$enable])	307	$json = $json->space_after ([$enable])
		308	$enabled = $json->get_space_after
273	If $enable is true (or missing), then the "encode" method will add	309	If $enable is true (or missing), then the "encode" method will add
274	an extra optional space after the ":" separating keys from values in	310	an extra optional space after the ":" separating keys from values in
275	JSON objects and extra whitespace after the "," separating key-value	311	JSON objects and extra whitespace after the "," separating key-value
276	pairs and array members.	312	pairs and array members.
277		313
…		…
283	Example, space_before and indent disabled, space_after enabled:	319	Example, space_before and indent disabled, space_after enabled:
284		320
285	{"key": "value"}	321	{"key": "value"}
286		322
287	$json = $json->relaxed ([$enable])	323	$json = $json->relaxed ([$enable])
		324	$enabled = $json->get_relaxed
288	If $enable is true (or missing), then "decode" will accept some	325	If $enable is true (or missing), then "decode" will accept some
289	extensions to normal JSON syntax (see below). "encode" will not be	326	extensions to normal JSON syntax (see below). "encode" will not be
290	affected in anyway. *Be aware that this option makes you accept	327	affected in anyway. *Be aware that this option makes you accept
291	invalid JSON texts as if they were valid!*. I suggest only to use	328	invalid JSON texts as if they were valid!*. I suggest only to use
292	this option to parse application-specific files written by humans	329	this option to parse application-specific files written by humans
…		…
295	If $enable is false (the default), then "decode" will only accept	332	If $enable is false (the default), then "decode" will only accept
296	valid JSON texts.	333	valid JSON texts.
297		334
298	Currently accepted extensions are:	335	Currently accepted extensions are:
299		336
300	* list items can have an end-comma	337	* list items can have an end-comma
		338
301	JSON separates array elements and key-value pairs with commas.	339	JSON separates array elements and key-value pairs with commas.
302	This can be annoying if you write JSON texts manually and want	340	This can be annoying if you write JSON texts manually and want
303	to be able to quickly append elements, so this extension accepts	341	to be able to quickly append elements, so this extension accepts
304	comma at the end of such items not just between them:	342	comma at the end of such items not just between them:
305		343
…		…
310	{	348	{
311	"k1": "v1",	349	"k1": "v1",
312	"k2": "v2", <- this comma not normally allowed	350	"k2": "v2", <- this comma not normally allowed
313	}	351	}
314		352
315	* shell-style '#'-comments	353	* shell-style '#'-comments
		354
316	Whenever JSON allows whitespace, shell-style comments are	355	Whenever JSON allows whitespace, shell-style comments are
317	additionally allowed. They are terminated by the first	356	additionally allowed. They are terminated by the first
318	carriage-return or line-feed character, after which more	357	carriage-return or line-feed character, after which more
319	white-space and comments are allowed.	358	white-space and comments are allowed.
320		359
…		…
322	1, # this comment not allowed in JSON	361	1, # this comment not allowed in JSON
323	# neither this one...	362	# neither this one...
324	]	363	]
325		364
326	$json = $json->canonical ([$enable])	365	$json = $json->canonical ([$enable])
		366	$enabled = $json->get_canonical
327	If $enable is true (or missing), then the "encode" method will	367	If $enable is true (or missing), then the "encode" method will
328	output JSON objects by sorting their keys. This is adding a	368	output JSON objects by sorting their keys. This is adding a
329	comparatively high overhead.	369	comparatively high overhead.
330		370
331	If $enable is false, then the "encode" method will output key-value	371	If $enable is false, then the "encode" method will output key-value
…		…
339	in Perl.	379	in Perl.
340		380
341	This setting has no effect when decoding JSON texts.	381	This setting has no effect when decoding JSON texts.
342		382
343	$json = $json->allow_nonref ([$enable])	383	$json = $json->allow_nonref ([$enable])
		384	$enabled = $json->get_allow_nonref
344	If $enable is true (or missing), then the "encode" method can	385	If $enable is true (or missing), then the "encode" method can
345	convert a non-reference into its corresponding string, number or	386	convert a non-reference into its corresponding string, number or
346	null JSON value, which is an extension to RFC4627. Likewise,	387	null JSON value, which is an extension to RFC4627. Likewise,
347	"decode" will accept those JSON values instead of croaking.	388	"decode" will accept those JSON values instead of croaking.
348		389
…		…
355	"allow_nonref", resulting in an invalid JSON text:	396	"allow_nonref", resulting in an invalid JSON text:
356		397
357	JSON::XS->new->allow_nonref->encode ("Hello, World!")	398	JSON::XS->new->allow_nonref->encode ("Hello, World!")
358	=> "Hello, World!"	399	=> "Hello, World!"
359		400
		401	$json = $json->allow_unknown ([$enable])
		402	$enabled = $json->get_allow_unknown
		403	If $enable is true (or missing), then "encode" will not throw an
		404	exception when it encounters values it cannot represent in JSON (for
		405	example, filehandles) but instead will encode a JSON "null" value.
		406	Note that blessed objects are not included here and are handled
		407	separately by c<allow_nonref>.
		408
		409	If $enable is false (the default), then "encode" will throw an
		410	exception when it encounters anything it cannot encode as JSON.
		411
		412	This option does not affect "decode" in any way, and it is
		413	recommended to leave it off unless you know your communications
		414	partner.
		415
360	$json = $json->allow_blessed ([$enable])	416	$json = $json->allow_blessed ([$enable])
		417	$enabled = $json->get_allow_blessed
361	If $enable is true (or missing), then the "encode" method will not	418	If $enable is true (or missing), then the "encode" method will not
362	barf when it encounters a blessed reference. Instead, the value of	419	barf when it encounters a blessed reference. Instead, the value of
363	the convert_blessed option will decide whether "null"	420	the convert_blessed option will decide whether "null"
364	("convert_blessed" disabled or no "to_json" method found) or a	421	("convert_blessed" disabled or no "TO_JSON" method found) or a
365	representation of the object ("convert_blessed" enabled and	422	representation of the object ("convert_blessed" enabled and
366	"to_json" method found) is being encoded. Has no effect on "decode".	423	"TO_JSON" method found) is being encoded. Has no effect on "decode".
367		424
368	If $enable is false (the default), then "encode" will throw an	425	If $enable is false (the default), then "encode" will throw an
369	exception when it encounters a blessed object.	426	exception when it encounters a blessed object.
370		427
371	$json = $json->convert_blessed ([$enable])	428	$json = $json->convert_blessed ([$enable])
		429	$enabled = $json->get_convert_blessed
372	If $enable is true (or missing), then "encode", upon encountering a	430	If $enable is true (or missing), then "encode", upon encountering a
373	blessed object, will check for the availability of the "TO_JSON"	431	blessed object, will check for the availability of the "TO_JSON"
374	method on the object's class. If found, it will be called in scalar	432	method on the object's class. If found, it will be called in scalar
375	context and the resulting scalar will be encoded instead of the	433	context and the resulting scalar will be encoded instead of the
376	object. If no "TO_JSON" method is found, the value of	434	object. If no "TO_JSON" method is found, the value of
…		…
380	returns other blessed objects, those will be handled in the same	438	returns other blessed objects, those will be handled in the same
381	way. "TO_JSON" must take care of not causing an endless recursion	439	way. "TO_JSON" must take care of not causing an endless recursion
382	cycle (== crash) in this case. The name of "TO_JSON" was chosen	440	cycle (== crash) in this case. The name of "TO_JSON" was chosen
383	because other methods called by the Perl core (== not by the user of	441	because other methods called by the Perl core (== not by the user of
384	the object) are usually in upper case letters and to avoid	442	the object) are usually in upper case letters and to avoid
385	collisions with the "to_json" function.	443	collisions with any "to_json" function or method.
386		444
387	This setting does not yet influence "decode" in any way, but in the	445	This setting does not yet influence "decode" in any way, but in the
388	future, global hooks might get installed that influence "decode" and	446	future, global hooks might get installed that influence "decode" and
389	are enabled by this setting.	447	are enabled by this setting.
390		448
…		…
466		524
467	{ __widget__ => $self->{id} }	525	{ __widget__ => $self->{id} }
468	}	526	}
469		527
470	$json = $json->shrink ([$enable])	528	$json = $json->shrink ([$enable])
		529	$enabled = $json->get_shrink
471	Perl usually over-allocates memory a bit when allocating space for	530	Perl usually over-allocates memory a bit when allocating space for
472	strings. This flag optionally resizes strings generated by either	531	strings. This flag optionally resizes strings generated by either
473	"encode" or "decode" to their minimum size possible. This can save	532	"encode" or "decode" to their minimum size possible. This can save
474	memory when your JSON texts are either very very long or you have	533	memory when your JSON texts are either very very long or you have
475	many short strings. It will also try to downgrade any strings to	534	many short strings. It will also try to downgrade any strings to
…		…
493	converting strings that look like integers or floats into integers	552	converting strings that look like integers or floats into integers
494	or floats internally (there is no difference on the Perl level),	553	or floats internally (there is no difference on the Perl level),
495	saving space.	554	saving space.
496		555
497	$json = $json->max_depth ([$maximum_nesting_depth])	556	$json = $json->max_depth ([$maximum_nesting_depth])
		557	$max_depth = $json->get_max_depth
498	Sets the maximum nesting level (default 512) accepted while encoding	558	Sets the maximum nesting level (default 512) accepted while encoding
499	or decoding. If the JSON text or Perl data structure has an equal or	559	or decoding. If a higher nesting level is detected in JSON text or a
500	higher nesting level then this limit, then the encoder and decoder	560	Perl data structure, then the encoder and decoder will stop and
501	will stop and croak at that point.	561	croak at that point.
502		562
503	Nesting level is defined by number of hash- or arrayrefs that the	563	Nesting level is defined by number of hash- or arrayrefs that the
504	encoder needs to traverse to reach a given point or the number of	564	encoder needs to traverse to reach a given point or the number of
505	"{" or "[" characters without their matching closing parenthesis	565	"{" or "[" characters without their matching closing parenthesis
506	crossed to reach a given character in a string.	566	crossed to reach a given character in a string.
507		567
508	Setting the maximum depth to one disallows any nesting, so that	568	Setting the maximum depth to one disallows any nesting, so that
509	ensures that the object is only a single hash/object or array.	569	ensures that the object is only a single hash/object or array.
510		570
511	The argument to "max_depth" will be rounded up to the next highest
512	power of two. If no argument is given, the highest possible setting	571	If no argument is given, the highest possible setting will be used,
513	will be used, which is rarely useful.	572	which is rarely useful.
		573
		574	Note that nesting is implemented by recursion in C. The default
		575	value has been chosen to be as large as typical operating systems
		576	allow without crashing.
514		577
515	See SECURITY CONSIDERATIONS, below, for more info on why this is	578	See SECURITY CONSIDERATIONS, below, for more info on why this is
516	useful.	579	useful.
517		580
518	$json = $json->max_size ([$maximum_string_size])	581	$json = $json->max_size ([$maximum_string_size])
		582	$max_size = $json->get_max_size
519	Set the maximum length a JSON text may have (in bytes) where	583	Set the maximum length a JSON text may have (in bytes) where
520	decoding is being attempted. The default is 0, meaning no limit.	584	decoding is being attempted. The default is 0, meaning no limit.
521	When "decode" is called on a string longer then this number of	585	When "decode" is called on a string that is longer then this many
522	characters it will not attempt to decode the string but throw an	586	bytes, it will not attempt to decode the string but throw an
523	exception. This setting has no effect on "encode" (yet).	587	exception. This setting has no effect on "encode" (yet).
524		588
525	The argument to "max_size" will be rounded up to the next highest
526	power of two (so may be more than requested). If no argument is
527	given, the limit check will be deactivated (same as when 0 is	589	If no argument is given, the limit check will be deactivated (same
528	specified).	590	as when 0 is specified).
529		591
530	See SECURITY CONSIDERATIONS, below, for more info on why this is	592	See SECURITY CONSIDERATIONS, below, for more info on why this is
531	useful.	593	useful.
532		594
533	$json_text = $json->encode ($perl_scalar)	595	$json_text = $json->encode ($perl_scalar)
…		…
558	and you need to know where the JSON text ends.	620	and you need to know where the JSON text ends.
559		621
560	JSON::XS->new->decode_prefix ("[1] the tail")	622	JSON::XS->new->decode_prefix ("[1] the tail")
561	=> ([], 3)	623	=> ([], 3)
562		624
		625	INCREMENTAL PARSING
		626	In some cases, there is the need for incremental parsing of JSON texts.
		627	While this module always has to keep both JSON text and resulting Perl
		628	data structure in memory at one time, it does allow you to parse a JSON
		629	stream incrementally. It does so by accumulating text until it has a
		630	full JSON object, which it then can decode. This process is similar to
		631	using "decode_prefix" to see if a full JSON object is available, but is
		632	much more efficient (and can be implemented with a minimum of method
		633	calls).
		634
		635	JSON::XS will only attempt to parse the JSON text once it is sure it has
		636	enough text to get a decisive result, using a very simple but truly
		637	incremental parser. This means that it sometimes won't stop as early as
		638	the full parser, for example, it doesn't detect parenthese mismatches.
		639	The only thing it guarantees is that it starts decoding as soon as a
		640	syntactically valid JSON text has been seen. This means you need to set
		641	resource limits (e.g. "max_size") to ensure the parser will stop parsing
		642	in the presence if syntax errors.
		643
		644	The following methods implement this incremental parser.
		645
		646	[void, scalar or list context] = $json->incr_parse ([$string])
		647	This is the central parsing function. It can both append new text
		648	and extract objects from the stream accumulated so far (both of
		649	these functions are optional).
		650
		651	If $string is given, then this string is appended to the already
		652	existing JSON fragment stored in the $json object.
		653
		654	After that, if the function is called in void context, it will
		655	simply return without doing anything further. This can be used to
		656	add more text in as many chunks as you want.
		657
		658	If the method is called in scalar context, then it will try to
		659	extract exactly one JSON object. If that is successful, it will
		660	return this object, otherwise it will return "undef". If there is a
		661	parse error, this method will croak just as "decode" would do (one
		662	can then use "incr_skip" to skip the errornous part). This is the
		663	most common way of using the method.
		664
		665	And finally, in list context, it will try to extract as many objects
		666	from the stream as it can find and return them, or the empty list
		667	otherwise. For this to work, there must be no separators between the
		668	JSON objects or arrays, instead they must be concatenated
		669	back-to-back. If an error occurs, an exception will be raised as in
		670	the scalar context case. Note that in this case, any
		671	previously-parsed JSON texts will be lost.
		672
		673	$lvalue_string = $json->incr_text
		674	This method returns the currently stored JSON fragment as an lvalue,
		675	that is, you can manipulate it. This only works when a preceding
		676	call to "incr_parse" in scalar context successfully returned an
		677	object. Under all other circumstances you must not call this
		678	function (I mean it. although in simple tests it might actually
		679	work, it will fail under real world conditions). As a special
		680	exception, you can also call this method before having parsed
		681	anything.
		682
		683	This function is useful in two cases: a) finding the trailing text
		684	after a JSON object or b) parsing multiple JSON objects separated by
		685	non-JSON text (such as commas).
		686
		687	$json->incr_skip
		688	This will reset the state of the incremental parser and will remove
		689	the parsed text from the input buffer so far. This is useful after
		690	"incr_parse" died, in which case the input buffer and incremental
		691	parser state is left unchanged, to skip the text parsed so far and
		692	to reset the parse state.
		693
		694	The difference to "incr_reset" is that only text until the parse
		695	error occured is removed.
		696
		697	$json->incr_reset
		698	This completely resets the incremental parser, that is, after this
		699	call, it will be as if the parser had never parsed anything.
		700
		701	This is useful if you want to repeatedly parse JSON objects and want
		702	to ignore any trailing data, which means you have to reset the
		703	parser after each successful decode.
		704
		705	LIMITATIONS
		706	All options that affect decoding are supported, except "allow_nonref".
		707	The reason for this is that it cannot be made to work sensibly: JSON
		708	objects and arrays are self-delimited, i.e. you can concatenate them
		709	back to back and still decode them perfectly. This does not hold true
		710	for JSON numbers, however.
		711
		712	For example, is the string 1 a single JSON number, or is it simply the
		713	start of 12? Or is 12 a single JSON number, or the concatenation of 1
		714	and 2? In neither case you can tell, and this is why JSON::XS takes the
		715	conservative route and disallows this case.
		716
		717	EXAMPLES
		718	Some examples will make all this clearer. First, a simple example that
		719	works similarly to "decode_prefix": We want to decode the JSON object at
		720	the start of a string and identify the portion after the JSON object:
		721
		722	my $text = "[1,2,3] hello";
		723
		724	my $json = new JSON::XS;
		725
		726	my $obj = $json->incr_parse ($text)
		727	or die "expected JSON object or array at beginning of string";
		728
		729	my $tail = $json->incr_text;
		730	# $tail now contains " hello"
		731
		732	Easy, isn't it?
		733
		734	Now for a more complicated example: Imagine a hypothetical protocol
		735	where you read some requests from a TCP stream, and each request is a
		736	JSON array, without any separation between them (in fact, it is often
		737	useful to use newlines as "separators", as these get interpreted as
		738	whitespace at the start of the JSON text, which makes it possible to
		739	test said protocol with "telnet"...).
		740
		741	Here is how you'd do it (it is trivial to write this in an event-based
		742	manner):
		743
		744	my $json = new JSON::XS;
		745
		746	# read some data from the socket
		747	while (sysread $socket, my $buf, 4096) {
		748
		749	# split and decode as many requests as possible
		750	for my $request ($json->incr_parse ($buf)) {
		751	# act on the $request
		752	}
		753	}
		754
		755	Another complicated example: Assume you have a string with JSON objects
		756	or arrays, all separated by (optional) comma characters (e.g. "[1],[2],
		757	[3]"). To parse them, we have to skip the commas between the JSON texts,
		758	and here is where the lvalue-ness of "incr_text" comes in useful:
		759
		760	my $text = "[1],[2], [3]";
		761	my $json = new JSON::XS;
		762
		763	# void context, so no parsing done
		764	$json->incr_parse ($text);
		765
		766	# now extract as many objects as possible. note the
		767	# use of scalar context so incr_text can be called.
		768	while (my $obj = $json->incr_parse) {
		769	# do something with $obj
		770
		771	# now skip the optional comma
		772	$json->incr_text =~ s/^ \s* , //x;
		773	}
		774
		775	Now lets go for a very complex example: Assume that you have a gigantic
		776	JSON array-of-objects, many gigabytes in size, and you want to parse it,
		777	but you cannot load it into memory fully (this has actually happened in
		778	the real world :).
		779
		780	Well, you lost, you have to implement your own JSON parser. But JSON::XS
		781	can still help you: You implement a (very simple) array parser and let
		782	JSON decode the array elements, which are all full JSON objects on their
		783	own (this wouldn't work if the array elements could be JSON numbers, for
		784	example):
		785
		786	my $json = new JSON::XS;
		787
		788	# open the monster
		789	open my $fh, "<bigfile.json"
		790	or die "bigfile: $!";
		791
		792	# first parse the initial "["
		793	for (;;) {
		794	sysread $fh, my $buf, 65536
		795	or die "read error: $!";
		796	$json->incr_parse ($buf); # void context, so no parsing
		797
		798	# Exit the loop once we found and removed(!) the initial "[".
		799	# In essence, we are (ab-)using the $json object as a simple scalar
		800	# we append data to.
		801	last if $json->incr_text =~ s/^ \s* \[ //x;
		802	}
		803
		804	# now we have the skipped the initial "[", so continue
		805	# parsing all the elements.
		806	for (;;) {
		807	# in this loop we read data until we got a single JSON object
		808	for (;;) {
		809	if (my $obj = $json->incr_parse) {
		810	# do something with $obj
		811	last;
		812	}
		813
		814	# add more data
		815	sysread $fh, my $buf, 65536
		816	or die "read error: $!";
		817	$json->incr_parse ($buf); # void context, so no parsing
		818	}
		819
		820	# in this loop we read data until we either found and parsed the
		821	# separating "," between elements, or the final "]"
		822	for (;;) {
		823	# first skip whitespace
		824	$json->incr_text =~ s/^\s*//;
		825
		826	# if we find "]", we are done
		827	if ($json->incr_text =~ s/^\]//) {
		828	print "finished.\n";
		829	exit;
		830	}
		831
		832	# if we find ",", we can continue with the next element
		833	if ($json->incr_text =~ s/^,//) {
		834	last;
		835	}
		836
		837	# if we find anything else, we have a parse error!
		838	if (length $json->incr_text) {
		839	die "parse error near ", $json->incr_text;
		840	}
		841
		842	# else add more data
		843	sysread $fh, my $buf, 65536
		844	or die "read error: $!";
		845	$json->incr_parse ($buf); # void context, so no parsing
		846	}
		847
		848	This is a complex example, but most of the complexity comes from the
		849	fact that we are trying to be correct (bear with me if I am wrong, I
		850	never ran the above example :).
		851
563	MAPPING	852	MAPPING
564	This section describes how JSON::XS maps Perl values to JSON values and	853	This section describes how JSON::XS maps Perl values to JSON values and
565	vice versa. These mappings are designed to "do the right thing" in most	854	vice versa. These mappings are designed to "do the right thing" in most
566	circumstances automatically, preserving round-tripping characteristics	855	circumstances automatically, preserving round-tripping characteristics
567	(what you put in comes out as something equivalent).	856	(what you put in comes out as something equivalent).
…		…
588	A JSON number becomes either an integer, numeric (floating point) or	877	A JSON number becomes either an integer, numeric (floating point) or
589	string scalar in perl, depending on its range and any fractional	878	string scalar in perl, depending on its range and any fractional
590	parts. On the Perl level, there is no difference between those as	879	parts. On the Perl level, there is no difference between those as
591	Perl handles all the conversion details, but an integer may take	880	Perl handles all the conversion details, but an integer may take
592	slightly less memory and might represent more values exactly than	881	slightly less memory and might represent more values exactly than
593	(floating point) numbers.	882	floating point numbers.
594		883
595	If the number consists of digits only, JSON::XS will try to	884	If the number consists of digits only, JSON::XS will try to
596	represent it as an integer value. If that fails, it will try to	885	represent it as an integer value. If that fails, it will try to
597	represent it as a numeric (floating point) value if that is possible	886	represent it as a numeric (floating point) value if that is possible
598	without loss of precision. Otherwise it will preserve the number as	887	without loss of precision. Otherwise it will preserve the number as
599	a string value.	888	a string value (in which case you lose roundtripping ability, as the
		889	JSON number will be re-encoded toa JSON string).
600		890
601	Numbers containing a fractional or exponential part will always be	891	Numbers containing a fractional or exponential part will always be
602	represented as numeric (floating point) values, possibly at a loss	892	represented as numeric (floating point) values, possibly at a loss
603	of precision.	893	of precision (in which case you might lose perfect roundtripping
604		894	ability, but the JSON number will still be re-encoded as a JSON
605	This might create round-tripping problems as numbers might become	895	number).
606	strings, but as Perl is typeless there is no other way to do it.
607		896
608	true, false	897	true, false
609	These JSON atoms become "JSON::XS::true" and "JSON::XS::false",	898	These JSON atoms become "JSON::XS::true" and "JSON::XS::false",
610	respectively. They are overloaded to act almost exactly like the	899	respectively. They are overloaded to act almost exactly like the
611	numbers 1 and 0. You can check whether a scalar is a JSON boolean by	900	numbers 1 and 0. You can check whether a scalar is a JSON boolean by
…		…
639	an exception to be thrown, except for references to the integers 0	928	an exception to be thrown, except for references to the integers 0
640	and 1, which get turned into "false" and "true" atoms in JSON. You	929	and 1, which get turned into "false" and "true" atoms in JSON. You
641	can also use "JSON::XS::false" and "JSON::XS::true" to improve	930	can also use "JSON::XS::false" and "JSON::XS::true" to improve
642	readability.	931	readability.
643		932
644	to_json [\0,JSON::XS::true] # yields [false,true]	933	encode_json [\0, JSON::XS::true] # yields [false,true]
645		934
646	JSON::XS::true, JSON::XS::false	935	JSON::XS::true, JSON::XS::false
647	These special values become JSON true and JSON false values,	936	These special values become JSON true and JSON false values,
648	respectively. You can also use "\1" and "\0" directly if you want.	937	respectively. You can also use "\1" and "\0" directly if you want.
649		938
650	blessed objects	939	blessed objects
651	Blessed objects are not allowed. JSON::XS currently tries to encode	940	Blessed objects are not directly representable in JSON. See the
652	their underlying representation (hash- or arrayref), but this	941	"allow_blessed" and "convert_blessed" methods on various options on
653	behaviour might change in future versions.	942	how to deal with this: basically, you can choose between throwing an
		943	exception, encoding the reference as if it weren't blessed, or
		944	provide your own serialiser method.
654		945
655	simple scalars	946	simple scalars
656	Simple Perl scalars (any scalar that is not a reference) are the	947	Simple Perl scalars (any scalar that is not a reference) are the
657	most difficult objects to encode: JSON::XS will encode undefined	948	most difficult objects to encode: JSON::XS will encode undefined
658	scalars as JSON null value, scalars that have last been used in a	949	scalars as JSON "null" values, scalars that have last been used in a
659	string context before encoding as JSON strings and anything else as	950	string context before encoding as JSON strings, and anything else as
660	number value:	951	number value:
661		952
662	# dump as number	953	# dump as number
663	to_json [2] # yields [2]	954	encode_json [2] # yields [2]
664	to_json [-3.0e17] # yields [-3e+17]	955	encode_json [-3.0e17] # yields [-3e+17]
665	my $value = 5; to_json [$value] # yields [5]	956	my $value = 5; encode_json [$value] # yields [5]
666		957
667	# used as string, so dump as string	958	# used as string, so dump as string
668	print $value;	959	print $value;
669	to_json [$value] # yields ["5"]	960	encode_json [$value] # yields ["5"]
670		961
671	# undef becomes null	962	# undef becomes null
672	to_json [undef] # yields [null]	963	encode_json [undef] # yields [null]
673		964
674	You can force the type to be a JSON string by stringifying it:	965	You can force the type to be a JSON string by stringifying it:
675		966
676	my $x = 3.1; # some variable containing a number	967	my $x = 3.1; # some variable containing a number
677	"$x"; # stringified	968	"$x"; # stringified
…		…
683	my $x = "3"; # some variable containing a string	974	my $x = "3"; # some variable containing a string
684	$x += 0; # numify it, ensuring it will be dumped as a number	975	$x += 0; # numify it, ensuring it will be dumped as a number
685	$x *= 1; # same thing, the choice is yours.	976	$x *= 1; # same thing, the choice is yours.
686		977
687	You can not currently force the type in other, less obscure, ways.	978	You can not currently force the type in other, less obscure, ways.
688	Tell me if you need this capability.	979	Tell me if you need this capability (but don't forget to explain why
		980	it's needed :).
689		981
690	COMPARISON	982	ENCODING/CODESET FLAG NOTES
691	As already mentioned, this module was created because none of the	983	The interested reader might have seen a number of flags that signify
692	existing JSON modules could be made to work correctly. First I will	984	encodings or codesets - "utf8", "latin1" and "ascii". There seems to be
693	describe the problems (or pleasures) I encountered with various existing	985	some confusion on what these do, so here is a short comparison:
694	JSON modules, followed by some benchmark values. JSON::XS was designed
695	not to suffer from any of these problems or limitations.
696		986
697	JSON 1.07	987	"utf8" controls whether the JSON text created by "encode" (and expected
698	Slow (but very portable, as it is written in pure Perl).	988	by "decode") is UTF-8 encoded or not, while "latin1" and "ascii" only
		989	control whether "encode" escapes character values outside their
		990	respective codeset range. Neither of these flags conflict with each
		991	other, although some combinations make less sense than others.
699		992
700	Undocumented/buggy Unicode handling (how JSON handles Unicode values	993	Care has been taken to make all flags symmetrical with respect to
701	is undocumented. One can get far by feeding it Unicode strings and	994	"encode" and "decode", that is, texts encoded with any combination of
702	doing en-/decoding oneself, but Unicode escapes are not working	995	these flag values will be correctly decoded when the same flags are used
		996	- in general, if you use different flag settings while encoding vs. when
		997	decoding you likely have a bug somewhere.
		998
		999	Below comes a verbose discussion of these flags. Note that a "codeset"
		1000	is simply an abstract set of character-codepoint pairs, while an
		1001	encoding takes those codepoint numbers and encodes them, in our case
		1002	into octets. Unicode is (among other things) a codeset, UTF-8 is an
		1003	encoding, and ISO-8859-1 (= latin 1) and ASCII are both codesets and
		1004	encodings at the same time, which can be confusing.
		1005
		1006	"utf8" flag disabled
		1007	When "utf8" is disabled (the default), then "encode"/"decode"
		1008	generate and expect Unicode strings, that is, characters with high
		1009	ordinal Unicode values (> 255) will be encoded as such characters,
		1010	and likewise such characters are decoded as-is, no canges to them
		1011	will be done, except "(re-)interpreting" them as Unicode codepoints
		1012	or Unicode characters, respectively (to Perl, these are the same
		1013	thing in strings unless you do funny/weird/dumb stuff).
		1014
		1015	This is useful when you want to do the encoding yourself (e.g. when
		1016	you want to have UTF-16 encoded JSON texts) or when some other layer
		1017	does the encoding for you (for example, when printing to a terminal
		1018	using a filehandle that transparently encodes to UTF-8 you certainly
		1019	do NOT want to UTF-8 encode your data first and have Perl encode it
		1020	another time).
		1021
		1022	"utf8" flag enabled
		1023	If the "utf8"-flag is enabled, "encode"/"decode" will encode all
		1024	characters using the corresponding UTF-8 multi-byte sequence, and
		1025	will expect your input strings to be encoded as UTF-8, that is, no
		1026	"character" of the input string must have any value > 255, as UTF-8
		1027	does not allow that.
		1028
		1029	The "utf8" flag therefore switches between two modes: disabled means
		1030	you will get a Unicode string in Perl, enabled means you get an
		1031	UTF-8 encoded octet/binary string in Perl.
		1032
		1033	"latin1" or "ascii" flags enabled
		1034	With "latin1" (or "ascii") enabled, "encode" will escape characters
		1035	with ordinal values > 255 (> 127 with "ascii") and encode the
		1036	remaining characters as specified by the "utf8" flag.
		1037
		1038	If "utf8" is disabled, then the result is also correctly encoded in
		1039	those character sets (as both are proper subsets of Unicode, meaning
		1040	that a Unicode string with all character values < 256 is the same
		1041	thing as a ISO-8859-1 string, and a Unicode string with all
		1042	character values < 128 is the same thing as an ASCII string in
703	properly).	1043	Perl).
704		1044
705	No round-tripping (strings get clobbered if they look like numbers,	1045	If "utf8" is enabled, you still get a correct UTF-8-encoded string,
706	e.g. the string 2.0 will encode to 2.0 instead of "2.0", and that	1046	regardless of these flags, just some more characters will be escaped
707	will decode into the number 2.	1047	using "\uXXXX" then before.
708		1048
709	JSON::PC 0.01	1049	Note that ISO-8859-1-encoded strings are not compatible with UTF-8
710	Very fast.	1050	encoding, while ASCII-encoded strings are. That is because the
		1051	ISO-8859-1 encoding is NOT a subset of UTF-8 (despite the ISO-8859-1
		1052	codeset being a subset of Unicode), while ASCII is.
711		1053
712	Undocumented/buggy Unicode handling.	1054	Surprisingly, "decode" will ignore these flags and so treat all
		1055	input values as governed by the "utf8" flag. If it is disabled, this
		1056	allows you to decode ISO-8859-1- and ASCII-encoded strings, as both
		1057	strict subsets of Unicode. If it is enabled, you can correctly
		1058	decode UTF-8 encoded strings.
713		1059
714	No round-tripping.	1060	So neither "latin1" nor "ascii" are incompatible with the "utf8"
		1061	flag - they only govern when the JSON output engine escapes a
		1062	character or not.
715		1063
716	Has problems handling many Perl values (e.g. regex results and other	1064	The main use for "latin1" is to relatively efficiently store binary
717	magic values will make it croak).	1065	data as JSON, at the expense of breaking compatibility with most
		1066	JSON decoders.
718		1067
719	Does not even generate valid JSON ("{1,2}" gets converted to "{1:2}"	1068	The main use for "ascii" is to force the output to not contain
720	which is not a valid JSON text.	1069	characters with values > 127, which means you can interpret the
		1070	resulting string as UTF-8, ISO-8859-1, ASCII, KOI8-R or most about
		1071	any character set and 8-bit-encoding, and still get the same data
		1072	structure back. This is useful when your channel for JSON transfer
		1073	is not 8-bit clean or the encoding might be mangled in between (e.g.
		1074	in mail), and works because ASCII is a proper subset of most 8-bit
		1075	and multibyte encodings in use in the world.
721		1076
722	Unmaintained (maintainer unresponsive for many months, bugs are not	1077	JSON and ECMAscript
723	getting fixed).	1078	JSON syntax is based on how literals are represented in javascript (the
		1079	not-standardised predecessor of ECMAscript) which is presumably why it
		1080	is called "JavaScript Object Notation".
724		1081
725	JSON::Syck 0.21	1082	However, JSON is not a subset (and also not a superset of course) of
726	Very buggy (often crashes).	1083	ECMAscript (the standard) or javascript (whatever browsers actually
		1084	implement).
727		1085
728	Very inflexible (no human-readable format supported, format pretty	1086	If you want to use javascript's "eval" function to "parse" JSON, you
729	much undocumented. I need at least a format for easy reading by	1087	might run into parse errors for valid JSON texts, or the resulting data
730	humans and a single-line compact format for use in a protocol, and	1088	structure might not be queryable:
731	preferably a way to generate ASCII-only JSON texts).
732		1089
733	Completely broken (and confusingly documented) Unicode handling	1090	One of the problems is that U+2028 and U+2029 are valid characters
734	(Unicode escapes are not working properly, you need to set	1091	inside JSON strings, but are not allowed in ECMAscript string literals,
735	ImplicitUnicode to different values on en- and decoding to get	1092	so the following Perl fragment will not output something that can be
736	symmetric behaviour).	1093	guaranteed to be parsable by javascript's "eval":
737		1094
738	No round-tripping (simple cases work, but this depends on whether	1095	use JSON::XS;
739	the scalar value was used in a numeric context or not).
740		1096
741	Dumping hashes may skip hash values depending on iterator state.	1097	print encode_json [chr 0x2028];
742		1098
743	Unmaintained (maintainer unresponsive for many months, bugs are not	1099	The right fix for this is to use a proper JSON parser in your javascript
744	getting fixed).	1100	programs, and not rely on "eval" (see for example Douglas Crockford's
		1101	json2.js parser).
745		1102
746	Does not check input for validity (i.e. will accept non-JSON input	1103	If this is not an option, you can, as a stop-gap measure, simply encode
747	and return "something" instead of raising an exception. This is a	1104	to ASCII-only JSON:
748	security issue: imagine two banks transferring money between each
749	other using JSON. One bank might parse a given non-JSON request and
750	deduct money, while the other might reject the transaction with a
751	syntax error. While a good protocol will at least recover, that is
752	extra unnecessary work and the transaction will still not succeed).
753		1105
754	JSON::DWIW 0.04	1106	use JSON::XS;
755	Very fast. Very natural. Very nice.
756		1107
757	Undocumented Unicode handling (but the best of the pack. Unicode	1108	print JSON::XS->new->ascii->encode ([chr 0x2028]);
758	escapes still don't get parsed properly).
759		1109
760	Very inflexible.	1110	Note that this will enlarge the resulting JSON text quite a bit if you
		1111	have many non-ASCII characters. You might be tempted to run some regexes
		1112	to only escape U+2028 and U+2029, e.g.:
761		1113
762	No round-tripping.	1114	# DO NOT USE THIS!
		1115	my $json = JSON::XS->new->utf8->encode ([chr 0x2028]);
		1116	$json =~ s/\xe2\x80\xa8/\\u2028/g; # escape U+2028
		1117	$json =~ s/\xe2\x80\xa9/\\u2029/g; # escape U+2029
		1118	print $json;
763		1119
764	Does not generate valid JSON texts (key strings are often unquoted,	1120	Note that this is a bad idea: the above only works for U+2028 and
765	empty keys result in nothing being output)	1121	U+2029 and thus only for fully ECMAscript-compliant parsers. Many
		1122	existing javascript implementations, however, have issues with other
		1123	characters as well - using "eval" naively simply will cause problems.
766		1124
767	Does not check input for validity.	1125	Another problem is that some javascript implementations reserve some
		1126	property names for their own purposes (which probably makes them
		1127	non-ECMAscript-compliant). For example, Iceweasel reserves the
		1128	"__proto__" property name for it's own purposes.
		1129
		1130	If that is a problem, you could parse try to filter the resulting JSON
		1131	output for these property strings, e.g.:
		1132
		1133	$json =~ s/"__proto__"\s*:/"__proto__renamed":/g;
		1134
		1135	This works because "__proto__" is not valid outside of strings, so every
		1136	occurence of ""__proto__"\s*:" must be a string used as property name.
		1137
		1138	If you know of other incompatibilities, please let me know.
768		1139
769	JSON and YAML	1140	JSON and YAML
770	You often hear that JSON is a subset (or a close subset) of YAML. This	1141	You often hear that JSON is a subset of YAML. This is, however, a mass
771	is, however, a mass hysteria and very far from the truth. In general,	1142	hysteria(*) and very far from the truth (as of the time of this
772	there is no way to configure JSON::XS to output a data structure as	1143	writing), so let me state it clearly: *in general, there is no way to
773	valid YAML.	1144	configure JSON::XS to output a data structure as valid YAML* that works
		1145	in all cases.
774		1146
775	If you really must use JSON::XS to generate YAML, you should use this	1147	If you really must use JSON::XS to generate YAML, you should use this
776	algorithm (subject to change in future versions):	1148	algorithm (subject to change in future versions):
777		1149
778	my $to_yaml = JSON::XS->new->utf8->space_after (1);	1150	my $to_yaml = JSON::XS->new->utf8->space_after (1);
779	my $yaml = $to_yaml->encode ($ref) . "\n";	1151	my $yaml = $to_yaml->encode ($ref) . "\n";
780		1152
781	This will usually generate JSON texts that also parse as valid YAML.	1153	This will usually generate JSON texts that also parse as valid YAML.
782	Please note that YAML has hardcoded limits on (simple) object key	1154	Please note that YAML has hardcoded limits on (simple) object key
783	lengths that JSON doesn't have, so you should make sure that your hash	1155	lengths that JSON doesn't have and also has different and incompatible
		1156	unicode handling, so you should make sure that your hash keys are
784	keys are noticeably shorter than the 1024 characters YAML allows.	1157	noticeably shorter than the 1024 "stream characters" YAML allows and
		1158	that you do not have characters with codepoint values outside the
		1159	Unicode BMP (basic multilingual page). YAML also does not allow "\/"
		1160	sequences in strings (which JSON::XS does not currently generate, but
		1161	other JSON generators might).
785		1162
786	There might be other incompatibilities that I am not aware of. In	1163	There might be other incompatibilities that I am not aware of (or the
		1164	YAML specification has been changed yet again - it does so quite often).
787	general you should not try to generate YAML with a JSON generator or	1165	In general you should not try to generate YAML with a JSON generator or
788	vice versa, or try to parse JSON with a YAML parser or vice versa:	1166	vice versa, or try to parse JSON with a YAML parser or vice versa:
789	chances are high that you will run into severe interoperability	1167	chances are high that you will run into severe interoperability problems
790	problems.	1168	when you least expect it.
		1169
		1170	(*) I have been pressured multiple times by Brian Ingerson (one of the
		1171	authors of the YAML specification) to remove this paragraph, despite
		1172	him acknowledging that the actual incompatibilities exist. As I was
		1173	personally bitten by this "JSON is YAML" lie, I refused and said I
		1174	will continue to educate people about these issues, so others do not
		1175	run into the same problem again and again. After this, Brian called
		1176	me a (quote)complete and worthless idiot(unquote).
		1177
		1178	In my opinion, instead of pressuring and insulting people who
		1179	actually clarify issues with YAML and the wrong statements of some
		1180	of its proponents, I would kindly suggest reading the JSON spec
		1181	(which is not that difficult or long) and finally make YAML
		1182	compatible to it, and educating users about the changes, instead of
		1183	spreading lies about the real compatibility for many years and
		1184	trying to silence people who point out that it isn't true.
791		1185
792	SPEED	1186	SPEED
793	It seems that JSON::XS is surprisingly fast, as shown in the following	1187	It seems that JSON::XS is surprisingly fast, as shown in the following
794	tables. They have been generated with the help of the "eg/bench" program	1188	tables. They have been generated with the help of the "eg/bench" program
795	in the JSON::XS distribution, to make it easy to compare on your own	1189	in the JSON::XS distribution, to make it easy to compare on your own
796	system.	1190	system.
797		1191
798	First comes a comparison between various modules using a very short	1192	First comes a comparison between various modules using a very short
799	single-line JSON string:	1193	single-line JSON string (also available at
		1194	<http://dist.schmorp.de/misc/json/short.json>).
800		1195
801	{"method": "handleMessage", "params": ["user1", "we were just talking"], \	1196	{"method": "handleMessage", "params": ["user1",
802	"id": null, "array":[1,11,234,-5,1e5,1e7, true, false]}	1197	"we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7,
		1198	true, false]}
803		1199
804	It shows the number of encodes/decodes per second (JSON::XS uses the	1200	It shows the number of encodes/decodes per second (JSON::XS uses the
805	functional interface, while JSON::XS/2 uses the OO interface with	1201	functional interface, while JSON::XS/2 uses the OO interface with
806	pretty-printing and hashkey sorting enabled, JSON::XS/3 enables shrink).	1202	pretty-printing and hashkey sorting enabled, JSON::XS/3 enables shrink).
807	Higher is better:	1203	Higher is better:
808		1204
809	Storable \| 15779.925 \| 14169.946 \|
810	-----------+------------+------------+
811	module \| encode \| decode \|	1205	module \| encode \| decode \|
812	-----------\|------------\|------------\|	1206	-----------\|------------\|------------\|
813	JSON \| 4990.842 \| 4088.813 \|	1207	JSON 1.x \| 4990.842 \| 4088.813 \|
814	JSON::DWIW \| 51653.990 \| 71575.154 \|	1208	JSON::DWIW \| 51653.990 \| 71575.154 \|
815	JSON::PC \| 65948.176 \| 74631.744 \|	1209	JSON::PC \| 65948.176 \| 74631.744 \|
816	JSON::PP \| 8931.652 \| 3817.168 \|	1210	JSON::PP \| 8931.652 \| 3817.168 \|
817	JSON::Syck \| 24877.248 \| 27776.848 \|	1211	JSON::Syck \| 24877.248 \| 27776.848 \|
818	JSON::XS \| 388361.481 \| 227951.304 \|	1212	JSON::XS \| 388361.481 \| 227951.304 \|
…		…
825	encoding, about three times faster on decoding, and over forty times	1219	encoding, about three times faster on decoding, and over forty times
826	faster than JSON, even with pretty-printing and key sorting. It also	1220	faster than JSON, even with pretty-printing and key sorting. It also
827	compares favourably to Storable for small amounts of data.	1221	compares favourably to Storable for small amounts of data.
828		1222
829	Using a longer test string (roughly 18KB, generated from Yahoo! Locals	1223	Using a longer test string (roughly 18KB, generated from Yahoo! Locals
830	search API (http://nanoref.com/yahooapis/mgPdGg):	1224	search API (<http://dist.schmorp.de/misc/json/long.json>).
831		1225
832	module \| encode \| decode \|	1226	module \| encode \| decode \|
833	-----------\|------------\|------------\|	1227	-----------\|------------\|------------\|
834	JSON \| 55.260 \| 34.971 \|	1228	JSON 1.x \| 55.260 \| 34.971 \|
835	JSON::DWIW \| 825.228 \| 1082.513 \|	1229	JSON::DWIW \| 825.228 \| 1082.513 \|
836	JSON::PC \| 3571.444 \| 2394.829 \|	1230	JSON::PC \| 3571.444 \| 2394.829 \|
837	JSON::PP \| 210.987 \| 32.574 \|	1231	JSON::PP \| 210.987 \| 32.574 \|
838	JSON::Syck \| 552.551 \| 787.544 \|	1232	JSON::Syck \| 552.551 \| 787.544 \|
839	JSON::XS \| 5780.463 \| 4854.519 \|	1233	JSON::XS \| 5780.463 \| 4854.519 \|
…		…
872	Third, JSON::XS recurses using the C stack when decoding objects and	1266	Third, JSON::XS recurses using the C stack when decoding objects and
873	arrays. The C stack is a limited resource: for instance, on my amd64	1267	arrays. The C stack is a limited resource: for instance, on my amd64
874	machine with 8MB of stack size I can decode around 180k nested arrays	1268	machine with 8MB of stack size I can decode around 180k nested arrays
875	but only 14k nested JSON objects (due to perl itself recursing deeply on	1269	but only 14k nested JSON objects (due to perl itself recursing deeply on
876	croak to free the temporary). If that is exceeded, the program crashes.	1270	croak to free the temporary). If that is exceeded, the program crashes.
877	to be conservative, the default nesting limit is set to 512. If your	1271	To be conservative, the default nesting limit is set to 512. If your
878	process has a smaller stack, you should adjust this setting accordingly	1272	process has a smaller stack, you should adjust this setting accordingly
879	with the "max_depth" method.	1273	with the "max_depth" method.
880		1274
881	And last but least, something else could bomb you that I forgot to think	1275	Something else could bomb you, too, that I forgot to think of. In that
882	of. In that case, you get to keep the pieces. I am always open for	1276	case, you get to keep the pieces. I am always open for hints, though...
883	hints, though...	1277
		1278	Also keep in mind that JSON::XS might leak contents of your Perl data
		1279	structures in its error messages, so when you serialise sensitive
		1280	information you might want to make sure that exceptions thrown by
		1281	JSON::XS will not end up in front of untrusted eyes.
884		1282
885	If you are using JSON::XS to return packets to consumption by JavaScript	1283	If you are using JSON::XS to return packets to consumption by JavaScript
886	scripts in a browser you should have a look at	1284	scripts in a browser you should have a look at
887	<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether	1285	<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether
888	you are vulnerable to some common attack vectors (which really are	1286	you are vulnerable to some common attack vectors (which really are
889	browser design bugs, but it is still you who will have to deal with it,	1287	browser design bugs, but it is still you who will have to deal with it,
890	as major browser developers care only for features, not about doing	1288	as major browser developers care only for features, not about getting
891	security right).	1289	security right).
892		1290
893	THREADS	1291	THREADS
894	This module is not guaranteed to be thread safe and there are no plans	1292	This module is not guaranteed to be thread safe and there are no plans
895	to change this until Perl gets thread support (as opposed to the	1293	to change this until Perl gets thread support (as opposed to the
896	horribly slow so-called "threads" which are simply slow and bloated	1294	horribly slow so-called "threads" which are simply slow and bloated
897	process simulations - use fork, its much faster, cheaper, better).	1295	process simulations - use fork, it's much faster, cheaper, better).
898		1296
899	(It might actually work, but you have been warned).	1297	(It might actually work, but you have been warned).
900		1298
901	BUGS	1299	BUGS
902	While the goal of this module is to be correct, that unfortunately does	1300	While the goal of this module is to be correct, that unfortunately does
903	not mean its bug-free, only that I think its design is bug-free. It is	1301	not mean it's bug-free, only that I think its design is bug-free. If you
904	still relatively early in its development. If you keep reporting bugs
905	they will be fixed swiftly, though.	1302	keep reporting bugs they will be fixed swiftly, though.
906		1303
907	Please refrain from using rt.cpan.org or any other bug reporting	1304	Please refrain from using rt.cpan.org or any other bug reporting
908	service. I put the contact address into my modules for a reason.	1305	service. I put the contact address into my modules for a reason.
		1306
		1307	SEE ALSO
		1308	The json_xs command line utility for quick experiments.
909		1309
910	AUTHOR	1310	AUTHOR
911	Marc Lehmann <schmorp@schmorp.de>	1311	Marc Lehmann <schmorp@schmorp.de>
912	http://home.schmorp.de/	1312	http://home.schmorp.de/
913		1313

Diff Legend

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

Comparing JSON-XS/README (file contents): Revision 1.20 by root, Tue Nov 13 22:59:08 2007 UTC vs. Revision 1.29 by root, Thu Feb 19 01:13:46 2009 UTC

Diff Legend

Comparing JSON-XS/README (file contents):
Revision 1.20 by root, Tue Nov 13 22:59:08 2007 UTC vs.
Revision 1.29 by root, Thu Feb 19 01:13:46 2009 UTC