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

Comparing JSON-XS/XS.pm (file contents):
Revision 1.41 by root, Mon Jun 11 03:45:26 2007 UTC vs.
Revision 1.67 by root, Mon Oct 15 01:22:34 2007 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	JSON::XS - JSON serialising/deserialising, done correctly and fast	3	JSON::XS - JSON serialising/deserialising, done correctly and fast
		4
		5	JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ
		6	(http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html)
4		7
5	=head1 SYNOPSIS	8	=head1 SYNOPSIS
6		9
7	use JSON::XS;	10	use JSON::XS;
8		11
9	# exported functions, they croak on error	12	# exported functions, they croak on error
10	# and expect/generate UTF-8	13	# and expect/generate UTF-8
11		14
12	$utf8_encoded_json_text = to_json $perl_hash_or_arrayref;	15	$utf8_encoded_json_text = to_json $perl_hash_or_arrayref;
13	$perl_hash_or_arrayref = from_json $utf8_encoded_json_text;	16	$perl_hash_or_arrayref = from_json $utf8_encoded_json_text;
14
15	# objToJson and jsonToObj aliases to to_json and from_json
16	# are exported for compatibility to the JSON module,
17	# but should not be used in new code.
18		17
19	# OO-interface	18	# OO-interface
20		19
21	$coder = JSON::XS->new->ascii->pretty->allow_nonref;	20	$coder = JSON::XS->new->ascii->pretty->allow_nonref;
22	$pretty_printed_unencoded = $coder->encode ($perl_scalar);	21	$pretty_printed_unencoded = $coder->encode ($perl_scalar);
85		84
86	package JSON::XS;	85	package JSON::XS;
87		86
88	use strict;	87	use strict;
89		88
90	BEGIN {
91	our $VERSION = '1.24';	89	our $VERSION = '1.52';
92	our @ISA = qw(Exporter);	90	our @ISA = qw(Exporter);
93		91
94	our @EXPORT = qw(to_json from_json objToJson jsonToObj);	92	our @EXPORT = qw(to_json from_json);
95	require Exporter;
96		93
97	require XSLoader;	94	use Exporter;
98	XSLoader::load JSON::XS::, $VERSION;	95	use XSLoader;
99	}
100		96
101	=head1 FUNCTIONAL INTERFACE	97	=head1 FUNCTIONAL INTERFACE
102		98
103	The following convinience methods are provided by this module. They are	99	The following convinience methods are provided by this module. They are
104	exported by default:	100	exported by default:
105		101
106	=over 4	102	=over 4
107		103
108	=item $json_text = to_json $perl_scalar	104	=item $json_text = to_json $perl_scalar
109		105
110	Converts the given Perl data structure (a simple scalar or a reference to	106	Converts the given Perl data structure to a UTF-8 encoded, binary string
111	a hash or array) to a UTF-8 encoded, binary string (that is, the string contains	107	(that is, the string contains octets only). Croaks on error.
112	octets only). Croaks on error.
113		108
114	This function call is functionally identical to:	109	This function call is functionally identical to:
115		110
116	$json_text = JSON::XS->new->utf8->encode ($perl_scalar)	111	$json_text = JSON::XS->new->utf8->encode ($perl_scalar)
117		112
118	except being faster.	113	except being faster.
119		114
120	=item $perl_scalar = from_json $json_text	115	=item $perl_scalar = from_json $json_text
121		116
122	The opposite of C<to_json>: expects an UTF-8 (binary) string and tries to	117	The opposite of C<to_json>: expects an UTF-8 (binary) string and tries
123	parse that as an UTF-8 encoded JSON text, returning the resulting simple	118	to parse that as an UTF-8 encoded JSON text, returning the resulting
124	scalar or reference. Croaks on error.	119	reference. Croaks on error.
125		120
126	This function call is functionally identical to:	121	This function call is functionally identical to:
127		122
128	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)	123	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)
129		124
130	except being faster.	125	except being faster.
131		126
		127	=item $is_boolean = JSON::XS::is_bool $scalar
		128
		129	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
		131	and are used to represent JSON C<true> and C<false> values in Perl.
		132
		133	See MAPPING, below, for more information on how JSON values are mapped to
		134	Perl.
		135
132	=back	136	=back
		137
		138
		139	=head1 A FEW NOTES ON UNICODE AND PERL
		140
		141	Since this often leads to confusion, here are a few very clear words on
		142	how Unicode works in Perl, modulo bugs.
		143
		144	=over 4
		145
		146	=item 1. Perl strings can store characters with ordinal values > 255.
		147
		148	This enables you to store unicode characters as single characters in a
		149	Perl string - very natural.
		150
		151	=item 2. Perl does I<not> associate an encoding with your strings.
		152
		153	Unless you force it to, e.g. when matching it against a regex, or printing
		154	the scalar to a file, in which case Perl either interprets your string as
		155	locale-encoded text, octets/binary, or as Unicode, depending on various
		156	settings. In no case is an encoding stored together with your data, it is
		157	I<use> that decides encoding, not any magical metadata.
		158
		159	=item 3. The internal utf-8 flag has no meaning with regards to the
		160	encoding of your string.
		161
		162	Just ignore that flag unless you debug a Perl bug, a module written in
		163	XS or want to dive into the internals of perl. Otherwise it will only
		164	confuse you, as, despite the name, it says nothing about how your string
		165	is encoded. You can have unicode strings with that flag set, with that
		166	flag clear, and you can have binary data with that flag set and that flag
		167	clear. Other possibilities exist, too.
		168
		169	If you didn't know about that flag, just the better, pretend it doesn't
		170	exist.
		171
		172	=item 4. A "Unicode String" is simply a string where each character can be
		173	validly interpreted as a Unicode codepoint.
		174
		175	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.
		177
		178	=item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string.
		179
		180	Its a fact. Learn to live with it.
		181
		182	=back
		183
		184	I hope this helps :)
133		185
134		186
135	=head1 OBJECT-ORIENTED INTERFACE	187	=head1 OBJECT-ORIENTED INTERFACE
136		188
137	The object oriented interface lets you configure your own encoding or	189	The object oriented interface lets you configure your own encoding or
…		…
276		328
277	Example, space_before and indent disabled, space_after enabled:	329	Example, space_before and indent disabled, space_after enabled:
278		330
279	{"key": "value"}	331	{"key": "value"}
280		332
		333	=item $json = $json->relaxed ([$enable])
		334
		335	If C<$enable> is true (or missing), then C<decode> will accept some
		336	extensions to normal JSON syntax (see below). C<encode> will not be
		337	affected in anyway. I<Be aware that this option makes you accept invalid
		338	JSON texts as if they were valid!>. I suggest only to use this option to
		339	parse application-specific files written by humans (configuration files,
		340	resource files etc.)
		341
		342	If C<$enable> is false (the default), then C<decode> will only accept
		343	valid JSON texts.
		344
		345	Currently accepted extensions are:
		346
		347	=over 4
		348
		349	=item * list items can have an end-comma
		350
		351	JSON I<separates> array elements and key-value pairs with commas. This
		352	can be annoying if you write JSON texts manually and want to be able to
		353	quickly append elements, so this extension accepts comma at the end of
		354	such items not just between them:
		355
		356	[
		357	1,
		358	2, <- this comma not normally allowed
		359	]
		360	{
		361	"k1": "v1",
		362	"k2": "v2", <- this comma not normally allowed
		363	}
		364
		365	=item * shell-style '#'-comments
		366
		367	Whenever JSON allows whitespace, shell-style comments are additionally
		368	allowed. They are terminated by the first carriage-return or line-feed
		369	character, after which more white-space and comments are allowed.
		370
		371	[
		372	1, # this comment not allowed in JSON
		373	# neither this one...
		374	]
		375
		376	=back
		377
281	=item $json = $json->canonical ([$enable])	378	=item $json = $json->canonical ([$enable])
282		379
283	If C<$enable> is true (or missing), then the C<encode> method will output JSON objects	380	If C<$enable> is true (or missing), then the C<encode> method will output JSON objects
284	by sorting their keys. This is adding a comparatively high overhead.	381	by sorting their keys. This is adding a comparatively high overhead.
285		382
…		…
309	Example, encode a Perl scalar as JSON value with enabled C<allow_nonref>,	406	Example, encode a Perl scalar as JSON value with enabled C<allow_nonref>,
310	resulting in an invalid JSON text:	407	resulting in an invalid JSON text:
311		408
312	JSON::XS->new->allow_nonref->encode ("Hello, World!")	409	JSON::XS->new->allow_nonref->encode ("Hello, World!")
313	=> "Hello, World!"	410	=> "Hello, World!"
		411
		412	=item $json = $json->allow_blessed ([$enable])
		413
		414	If C<$enable> is true (or missing), then the C<encode> method will not
		415	barf when it encounters a blessed reference. Instead, the value of the
		416	B<convert_blessed> option will decide wether C<null> (C<convert_blessed>
		417	disabled or no C<to_json> method found) or a representation of the
		418	object (C<convert_blessed> enabled and C<to_json> method found) is being
		419	encoded. Has no effect on C<decode>.
		420
		421	If C<$enable> is false (the default), then C<encode> will throw an
		422	exception when it encounters a blessed object.
		423
		424	=item $json = $json->convert_blessed ([$enable])
		425
		426	If C<$enable> is true (or missing), then C<encode>, upon encountering a
		427	blessed object, will check for the availability of the C<TO_JSON> method
		428	on the object's class. If found, it will be called in scalar context
		429	and the resulting scalar will be encoded instead of the object. If no
		430	C<TO_JSON> method is found, the value of C<allow_blessed> will decide what
		431	to do.
		432
		433	The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON>
		434	returns other blessed objects, those will be handled in the same
		435	way. C<TO_JSON> must take care of not causing an endless recursion cycle
		436	(== crash) in this case. The name of C<TO_JSON> was chosen because other
		437	methods called by the Perl core (== not by the user of the object) are
		438	usually in upper case letters and to avoid collisions with the C<to_json>
		439	function.
		440
		441	This setting does not yet influence C<decode> in any way, but in the
		442	future, global hooks might get installed that influence C<decode> and are
		443	enabled by this setting.
		444
		445	If C<$enable> is false, then the C<allow_blessed> setting will decide what
		446	to do when a blessed object is found.
		447
		448	=item $json = $json->filter_json_object ([$coderef->($hashref)])
		449
		450	When C<$coderef> is specified, it will be called from C<decode> each
		451	time it decodes a JSON object. The only argument is a reference to the
		452	newly-created hash. If the code references returns a single scalar (which
		453	need not be a reference), this value (i.e. a copy of that scalar to avoid
		454	aliasing) is inserted into the deserialised data structure. If it returns
		455	an empty list (NOTE: I<not> C<undef>, which is a valid scalar), the
		456	original deserialised hash will be inserted. This setting can slow down
		457	decoding considerably.
		458
		459	When C<$coderef> is omitted or undefined, any existing callback will
		460	be removed and C<decode> will not change the deserialised hash in any
		461	way.
		462
		463	Example, convert all JSON objects into the integer 5:
		464
		465	my $js = JSON::XS->new->filter_json_object (sub { 5 });
		466	# returns [5]
		467	$js->decode ('[{}]')
		468	# throw an exception because allow_nonref is not enabled
		469	# so a lone 5 is not allowed.
		470	$js->decode ('{"a":1, "b":2}');
		471
		472	=item $json = $json->filter_json_single_key_object ($key [=> $coderef->($value)])
		473
		474	Works remotely similar to C<filter_json_object>, but is only called for
		475	JSON objects having a single key named C<$key>.
		476
		477	This C<$coderef> is called before the one specified via
		478	C<filter_json_object>, if any. It gets passed the single value in the JSON
		479	object. If it returns a single value, it will be inserted into the data
		480	structure. If it returns nothing (not even C<undef> but the empty list),
		481	the callback from C<filter_json_object> will be called next, as if no
		482	single-key callback were specified.
		483
		484	If C<$coderef> is omitted or undefined, the corresponding callback will be
		485	disabled. There can only ever be one callback for a given key.
		486
		487	As this callback gets called less often then the C<filter_json_object>
		488	one, decoding speed will not usually suffer as much. Therefore, single-key
		489	objects make excellent targets to serialise Perl objects into, especially
		490	as single-key JSON objects are as close to the type-tagged value concept
		491	as JSON gets (its basically an ID/VALUE tuple). Of course, JSON does not
		492	support this in any way, so you need to make sure your data never looks
		493	like a serialised Perl hash.
		494
		495	Typical names for the single object key are C<__class_whatever__>, or
		496	C<$__dollars_are_rarely_used__$> or C<}ugly_brace_placement>, or even
		497	things like C<__class_md5sum(classname)__>, to reduce the risk of clashing
		498	with real hashes.
		499
		500	Example, decode JSON objects of the form C<< { "__widget__" => <id> } >>
		501	into the corresponding C<< $WIDGET{<id>} >> object:
		502
		503	# return whatever is in $WIDGET{5}:
		504	JSON::XS
		505	->new
		506	->filter_json_single_key_object (__widget__ => sub {
		507	$WIDGET{ $_[0] }
		508	})
		509	->decode ('{"__widget__": 5')
		510
		511	# this can be used with a TO_JSON method in some "widget" class
		512	# for serialisation to json:
		513	sub WidgetBase::TO_JSON {
		514	my ($self) = @_;
		515
		516	unless ($self->{id}) {
		517	$self->{id} = ..get..some..id..;
		518	$WIDGET{$self->{id}} = $self;
		519	}
		520
		521	{ __widget__ => $self->{id} }
		522	}
314		523
315	=item $json = $json->shrink ([$enable])	524	=item $json = $json->shrink ([$enable])
316		525
317	Perl usually over-allocates memory a bit when allocating space for	526	Perl usually over-allocates memory a bit when allocating space for
318	strings. This flag optionally resizes strings generated by either	527	strings. This flag optionally resizes strings generated by either
…		…
351	given character in a string.	560	given character in a string.
352		561
353	Setting the maximum depth to one disallows any nesting, so that ensures	562	Setting the maximum depth to one disallows any nesting, so that ensures
354	that the object is only a single hash/object or array.	563	that the object is only a single hash/object or array.
355		564
356	The argument to C<max_depth> will be rounded up to the next nearest power	565	The argument to C<max_depth> will be rounded up to the next highest power
357	of two.	566	of two. If no argument is given, the highest possible setting will be
		567	used, which is rarely useful.
		568
		569	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
		570
		571	=item $json = $json->max_size ([$maximum_string_size])
		572
		573	Set the maximum length a JSON text may have (in bytes) where decoding is
		574	being attempted. The default is C<0>, meaning no limit. When C<decode>
		575	is called on a string longer then this number of characters it will not
		576	attempt to decode the string but throw an exception. This setting has no
		577	effect on C<encode> (yet).
		578
		579	The argument to C<max_size> will be rounded up to the next B<highest>
		580	power of two (so may be more than requested). If no argument is given, the
		581	limit check will be deactivated (same as when C<0> is specified).
358		582
359	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.	583	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
360		584
361	=item $json_text = $json->encode ($perl_scalar)	585	=item $json_text = $json->encode ($perl_scalar)
362		586
…		…
424	are represented by the same codepoints in the Perl string, so no manual	648	are represented by the same codepoints in the Perl string, so no manual
425	decoding is necessary.	649	decoding is necessary.
426		650
427	=item number	651	=item number
428		652
429	A JSON number becomes either an integer or numeric (floating point)	653	A JSON number becomes either an integer, numeric (floating point) or
430	scalar in perl, depending on its range and any fractional parts. On the	654	string scalar in perl, depending on its range and any fractional parts. On
431	Perl level, there is no difference between those as Perl handles all the	655	the Perl level, there is no difference between those as Perl handles all
432	conversion details, but an integer may take slightly less memory and might	656	the conversion details, but an integer may take slightly less memory and
433	represent more values exactly than (floating point) numbers.	657	might represent more values exactly than (floating point) numbers.
		658
		659	If the number consists of digits only, JSON::XS will try to represent
		660	it as an integer value. If that fails, it will try to represent it as
		661	a numeric (floating point) value if that is possible without loss of
		662	precision. Otherwise it will preserve the number as a string value.
		663
		664	Numbers containing a fractional or exponential part will always be
		665	represented as numeric (floating point) values, possibly at a loss of
		666	precision.
		667
		668	This might create round-tripping problems as numbers might become strings,
		669	but as Perl is typeless there is no other way to do it.
434		670
435	=item true, false	671	=item true, false
436		672
437	These JSON atoms become C<0>, C<1>, respectively. Information is lost in	673	These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>,
438	this process. Future versions might represent those values differently,	674	respectively. They are overloaded to act almost exactly like the numbers
439	but they will be guarenteed to act like these integers would normally in	675	C<1> and C<0>. You can check wether a scalar is a JSON boolean by using
440	Perl.	676	the C<JSON::XS::is_bool> function.
441		677
442	=item null	678	=item null
443		679
444	A JSON null atom becomes C<undef> in Perl.	680	A JSON null atom becomes C<undef> in Perl.
445		681
…		…
477	C<1>, which get turned into C<false> and C<true> atoms in JSON. You can	713	C<1>, which get turned into C<false> and C<true> atoms in JSON. You can
478	also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability.	714	also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability.
479		715
480	to_json [\0,JSON::XS::true] # yields [false,true]	716	to_json [\0,JSON::XS::true] # yields [false,true]
481		717
		718	=item JSON::XS::true, JSON::XS::false
		719
		720	These special values become JSON true and JSON false values,
		721	respectively. You can also use C<\1> and C<\0> directly if you want.
		722
482	=item blessed objects	723	=item blessed objects
483		724
484	Blessed objects are not allowed. JSON::XS currently tries to encode their	725	Blessed objects are not allowed. JSON::XS currently tries to encode their
485	underlying representation (hash- or arrayref), but this behaviour might	726	underlying representation (hash- or arrayref), but this behaviour might
486	change in future versions.	727	change in future versions.
…		…
649	It shows the number of encodes/decodes per second (JSON::XS uses	890	It shows the number of encodes/decodes per second (JSON::XS uses
650	the functional interface, while JSON::XS/2 uses the OO interface	891	the functional interface, while JSON::XS/2 uses the OO interface
651	with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables	892	with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables
652	shrink). Higher is better:	893	shrink). Higher is better:
653		894
		895	Storable \| 15779.925 \| 14169.946 \|
		896	-----------+------------+------------+
654	module \| encode \| decode \|	897	module \| encode \| decode \|
655	-----------\|------------\|------------\|	898	-----------\|------------\|------------\|
656	JSON \| 7645.468 \| 4208.613 \|	899	JSON \| 4990.842 \| 4088.813 \|
657	JSON::DWIW \| 40721.398 \| 77101.176 \|	900	JSON::DWIW \| 51653.990 \| 71575.154 \|
658	JSON::PC \| 65948.176 \| 78251.940 \|	901	JSON::PC \| 65948.176 \| 74631.744 \|
659	JSON::Syck \| 22844.793 \| 26479.192 \|	902	JSON::PP \| 8931.652 \| 3817.168 \|
		903	JSON::Syck \| 24877.248 \| 27776.848 \|
660	JSON::XS \| 388361.481 \| 199728.762 \|	904	JSON::XS \| 388361.481 \| 227951.304 \|
661	JSON::XS/2 \| 218453.333 \| 192399.266 \|	905	JSON::XS/2 \| 227951.304 \| 218453.333 \|
662	JSON::XS/3 \| 338250.323 \| 192399.266 \|	906	JSON::XS/3 \| 338250.323 \| 218453.333 \|
663	Storable \| 15779.925 \| 14169.946 \|	907	Storable \| 16500.016 \| 135300.129 \|
664	-----------+------------+------------+	908	-----------+------------+------------+
665		909
666	That is, JSON::XS is about five times faster than JSON::DWIW on encoding,	910	That is, JSON::XS is about five times faster than JSON::DWIW on encoding,
667	about three times faster on decoding, and over fourty times faster	911	about three times faster on decoding, and over fourty times faster
668	than JSON, even with pretty-printing and key sorting. It also compares	912	than JSON, even with pretty-printing and key sorting. It also compares
…		…
671	Using a longer test string (roughly 18KB, generated from Yahoo! Locals	915	Using a longer test string (roughly 18KB, generated from Yahoo! Locals
672	search API (http://nanoref.com/yahooapis/mgPdGg):	916	search API (http://nanoref.com/yahooapis/mgPdGg):
673		917
674	module \| encode \| decode \|	918	module \| encode \| decode \|
675	-----------\|------------\|------------\|	919	-----------\|------------\|------------\|
676	JSON \| 254.685 \| 37.665 \|	920	JSON \| 55.260 \| 34.971 \|
677	JSON::DWIW \| 843.343 \| 1049.731 \|	921	JSON::DWIW \| 825.228 \| 1082.513 \|
678	JSON::PC \| 3602.116 \| 2307.352 \|	922	JSON::PC \| 3571.444 \| 2394.829 \|
		923	JSON::PP \| 210.987 \| 32.574 \|
679	JSON::Syck \| 505.107 \| 787.899 \|	924	JSON::Syck \| 552.551 \| 787.544 \|
680	JSON::XS \| 5747.196 \| 3690.220 \|	925	JSON::XS \| 5780.463 \| 4854.519 \|
681	JSON::XS/2 \| 3968.121 \| 3676.634 \|	926	JSON::XS/2 \| 3869.998 \| 4798.975 \|
682	JSON::XS/3 \| 6105.246 \| 3662.508 \|	927	JSON::XS/3 \| 5862.880 \| 4798.975 \|
683	Storable \| 4417.337 \| 5285.161 \|	928	Storable \| 4445.002 \| 5235.027 \|
684	-----------+------------+------------+	929	-----------+------------+------------+
685		930
686	Again, JSON::XS leads by far (except for Storable which non-surprisingly	931	Again, JSON::XS leads by far (except for Storable which non-surprisingly
687	decodes faster).	932	decodes faster).
688		933
…		…
705	Second, you need to avoid resource-starving attacks. That means you should	950	Second, you need to avoid resource-starving attacks. That means you should
706	limit the size of JSON texts you accept, or make sure then when your	951	limit the size of JSON texts you accept, or make sure then when your
707	resources run out, thats just fine (e.g. by using a separate process that	952	resources run out, thats just fine (e.g. by using a separate process that
708	can crash safely). The size of a JSON text in octets or characters is	953	can crash safely). The size of a JSON text in octets or characters is
709	usually a good indication of the size of the resources required to decode	954	usually a good indication of the size of the resources required to decode
710	it into a Perl structure.	955	it into a Perl structure. While JSON::XS can check the size of the JSON
		956	text, it might be too late when you already have it in memory, so you
		957	might want to check the size before you accept the string.
711		958
712	Third, JSON::XS recurses using the C stack when decoding objects and	959	Third, JSON::XS recurses using the C stack when decoding objects and
713	arrays. The C stack is a limited resource: for instance, on my amd64	960	arrays. The C stack is a limited resource: for instance, on my amd64
714	machine with 8MB of stack size I can decode around 180k nested arrays but	961	machine with 8MB of stack size I can decode around 180k nested arrays but
715	only 14k nested JSON objects (due to perl itself recursing deeply on croak	962	only 14k nested JSON objects (due to perl itself recursing deeply on croak
…		…
720		967
721	And last but least, something else could bomb you that I forgot to think	968	And last but least, something else could bomb you that I forgot to think
722	of. In that case, you get to keep the pieces. I am always open for hints,	969	of. In that case, you get to keep the pieces. I am always open for hints,
723	though...	970	though...
724		971
		972	If you are using JSON::XS to return packets to consumption
		973	by javascript scripts in a browser you should have a look at
		974	L<http://jpsykes.com/47/practical-csrf-and-json-security> to see wether
		975	you are vulnerable to some common attack vectors (which really are browser
		976	design bugs, but it is still you who will have to deal with it, as major
		977	browser developers care only for features, not about doing security
		978	right).
		979
		980
		981	=head1 THREADS
		982
		983	This module is I<not> guarenteed to be thread safe and there are no
		984	plans to change this until Perl gets thread support (as opposed to the
		985	horribly slow so-called "threads" which are simply slow and bloated
		986	process simulations - use fork, its I<much> faster, cheaper, better).
		987
		988	(It might actually work, but you ahve ben warned).
		989
725		990
726	=head1 BUGS	991	=head1 BUGS
727		992
728	While the goal of this module is to be correct, that unfortunately does	993	While the goal of this module is to be correct, that unfortunately does
729	not mean its bug-free, only that I think its design is bug-free. It is	994	not mean its bug-free, only that I think its design is bug-free. It is
730	still relatively early in its development. If you keep reporting bugs they	995	still relatively early in its development. If you keep reporting bugs they
731	will be fixed swiftly, though.	996	will be fixed swiftly, though.
732		997
		998	Please refrain from using rt.cpan.org or any other bug reporting
		999	service. I put the contact address into my modules for a reason.
		1000
733	=cut	1001	=cut
734		1002
		1003	our $true = do { bless \(my $dummy = 1), "JSON::XS::Boolean" };
		1004	our $false = do { bless \(my $dummy = 0), "JSON::XS::Boolean" };
		1005
735	sub true() { \1 }	1006	sub true() { $true }
736	sub false() { \0 }	1007	sub false() { $false }
		1008
		1009	sub is_bool($) {
		1010	UNIVERSAL::isa $_[0], "JSON::XS::Boolean"
		1011	# or UNIVERSAL::isa $_[0], "JSON::Literal"
		1012	}
		1013
		1014	XSLoader::load "JSON::XS", $VERSION;
		1015
		1016	package JSON::XS::Boolean;
		1017
		1018	use overload
		1019	"0+" => sub { ${$_[0]} },
		1020	"++" => sub { $_[0] = ${$_[0]} + 1 },
		1021	"--" => sub { $_[0] = ${$_[0]} - 1 },
		1022	fallback => 1;
737		1023
738	1;	1024	1;
739		1025
740	=head1 AUTHOR	1026	=head1 AUTHOR
741		1027

Diff Legend

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

Comparing JSON-XS/XS.pm (file contents): Revision 1.41 by root, Mon Jun 11 03:45:26 2007 UTC vs. Revision 1.67 by root, Mon Oct 15 01:22:34 2007 UTC

Diff Legend

Comparing JSON-XS/XS.pm (file contents):
Revision 1.41 by root, Mon Jun 11 03:45:26 2007 UTC vs.
Revision 1.67 by root, Mon Oct 15 01:22:34 2007 UTC