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

Comparing CBOR-XS/XS.pm (file contents):
Revision 1.28 by root, Thu Nov 28 16:09:04 2013 UTC vs.
Revision 1.66 by root, Tue Jun 27 02:03:24 2017 UTC

…		…
48	Regarding compactness, C<CBOR::XS>-encoded data structures are usually	48	Regarding compactness, C<CBOR::XS>-encoded data structures are usually
49	about 20% smaller than the same data encoded as (compact) JSON or	49	about 20% smaller than the same data encoded as (compact) JSON or
50	L<Storable>.	50	L<Storable>.
51		51
52	In addition to the core CBOR data format, this module implements a	52	In addition to the core CBOR data format, this module implements a
53	number of extensions, to support cyclic and shared data structures (see	53	number of extensions, to support cyclic and shared data structures
54	C<allow_sharing>), string deduplication (see C<pack_strings>) and scalar	54	(see C<allow_sharing> and C<allow_cycles>), string deduplication (see
55	references (always enabled).	55	C<pack_strings>) and scalar references (always enabled).
56		56
57	The primary goal of this module is to be I<correct> and the secondary goal	57	The primary goal of this module is to be I<correct> and the secondary goal
58	is to be I<fast>. To reach the latter goal it was written in C.	58	is to be I<fast>. To reach the latter goal it was written in C.
59		59
60	See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and	60	See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and
…		…
64		64
65	package CBOR::XS;	65	package CBOR::XS;
66		66
67	use common::sense;	67	use common::sense;
68		68
69	our $VERSION = '1.0';	69	our $VERSION = 1.7;
70	our @ISA = qw(Exporter);	70	our @ISA = qw(Exporter);
71		71
72	our @EXPORT = qw(encode_cbor decode_cbor);	72	our @EXPORT = qw(encode_cbor decode_cbor);
73		73
74	use Exporter;	74	use Exporter;
…		…
112		112
113	The mutators for flags all return the CBOR object again and thus calls can	113	The mutators for flags all return the CBOR object again and thus calls can
114	be chained:	114	be chained:
115		115
116	my $cbor = CBOR::XS->new->encode ({a => [1,2]});	116	my $cbor = CBOR::XS->new->encode ({a => [1,2]});
		117
		118	=item $cbor = new_safe CBOR::XS
		119
		120	Create a new, safe/secure CBOR::XS object. This is similar to C<new>,
		121	but configures the coder object to be safe to use with untrusted
		122	data. Currently, this is equivalent to:
		123
		124	my $cbor = CBOR::XS
		125	->new
		126	->forbid_objects
		127	->filter (\&CBOR::XS::safe_filter)
		128	->max_size (1e8);
		129
		130	But is more future proof (it is better to crash because of a change than
		131	to be exploited in other ways).
		132
		133	=cut
		134
		135	sub new_safe {
		136	CBOR::XS
		137	->new
		138	->forbid_objects
		139	->filter (\&CBOR::XS::safe_filter)
		140	->max_size (1e8)
		141	}
117		142
118	=item $cbor = $cbor->max_depth ([$maximum_nesting_depth])	143	=item $cbor = $cbor->max_depth ([$maximum_nesting_depth])
119		144
120	=item $max_depth = $cbor->get_max_depth	145	=item $max_depth = $cbor->get_max_depth
121		146
…		…
137		162
138	Note that nesting is implemented by recursion in C. The default value has	163	Note that nesting is implemented by recursion in C. The default value has
139	been chosen to be as large as typical operating systems allow without	164	been chosen to be as large as typical operating systems allow without
140	crashing.	165	crashing.
141		166
142	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.	167	See L<SECURITY CONSIDERATIONS>, below, for more info on why this is useful.
143		168
144	=item $cbor = $cbor->max_size ([$maximum_string_size])	169	=item $cbor = $cbor->max_size ([$maximum_string_size])
145		170
146	=item $max_size = $cbor->get_max_size	171	=item $max_size = $cbor->get_max_size
147		172
…		…
152	effect on C<encode> (yet).	177	effect on C<encode> (yet).
153		178
154	If no argument is given, the limit check will be deactivated (same as when	179	If no argument is given, the limit check will be deactivated (same as when
155	C<0> is specified).	180	C<0> is specified).
156		181
157	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.	182	See L<SECURITY CONSIDERATIONS>, below, for more info on why this is useful.
158		183
159	=item $cbor = $cbor->allow_unknown ([$enable])	184	=item $cbor = $cbor->allow_unknown ([$enable])
160		185
161	=item $enabled = $cbor->get_allow_unknown	186	=item $enabled = $cbor->get_allow_unknown
162		187
…		…
180	reference to the earlier value.	205	reference to the earlier value.
181		206
182	This means that such values will only be encoded once, and will not result	207	This means that such values will only be encoded once, and will not result
183	in a deep cloning of the value on decode, in decoders supporting the value	208	in a deep cloning of the value on decode, in decoders supporting the value
184	sharing extension. This also makes it possible to encode cyclic data	209	sharing extension. This also makes it possible to encode cyclic data
185	structures.	210	structures (which need C<allow_cycles> to be enabled to be decoded by this
		211	module).
186		212
187	It is recommended to leave it off unless you know your	213	It is recommended to leave it off unless you know your
188	communication partner supports the value sharing extensions to CBOR	214	communication partner supports the value sharing extensions to CBOR
189	(L<http://cbor.schmorp.de/value-sharing>), as without decoder support, the	215	(L<http://cbor.schmorp.de/value-sharing>), as without decoder support, the
190	resulting data structure might be unusable.	216	resulting data structure might be unusable.
191		217
192	Detecting shared values incurs a runtime overhead when values are encoded	218	Detecting shared values incurs a runtime overhead when values are encoded
193	that have a reference counter large than one, and might unnecessarily	219	that have a reference counter large than one, and might unnecessarily
194	increase the encoded size, as potentially shared values are encode as	220	increase the encoded size, as potentially shared values are encode as
195	sharable whether or not they are actually shared.	221	shareable whether or not they are actually shared.
196		222
197	At the moment, only targets of references can be shared (e.g. scalars,	223	At the moment, only targets of references can be shared (e.g. scalars,
198	arrays or hashes pointed to by a reference). Weirder constructs, such as	224	arrays or hashes pointed to by a reference). Weirder constructs, such as
199	an array with multiple "copies" of the I<same> string, which are hard but	225	an array with multiple "copies" of the I<same> string, which are hard but
200	not impossible to create in Perl, are not supported (this is the same as	226	not impossible to create in Perl, are not supported (this is the same as
…		…
205	structures cannot be encoded in this mode.	231	structures cannot be encoded in this mode.
206		232
207	This option does not affect C<decode> in any way - shared values and	233	This option does not affect C<decode> in any way - shared values and
208	references will always be decoded properly if present.	234	references will always be decoded properly if present.
209		235
		236	=item $cbor = $cbor->allow_cycles ([$enable])
		237
		238	=item $enabled = $cbor->get_allow_cycles
		239
		240	If C<$enable> is true (or missing), then C<decode> will happily decode
		241	self-referential (cyclic) data structures. By default these will not be
		242	decoded, as they need manual cleanup to avoid memory leaks, so code that
		243	isn't prepared for this will not leak memory.
		244
		245	If C<$enable> is false (the default), then C<decode> will throw an error
		246	when it encounters a self-referential/cyclic data structure.
		247
		248	FUTURE DIRECTION: the motivation behind this option is to avoid I<real>
		249	cycles - future versions of this module might chose to decode cyclic data
		250	structures using weak references when this option is off, instead of
		251	throwing an error.
		252
		253	This option does not affect C<encode> in any way - shared values and
		254	references will always be encoded properly if present.
		255
		256	=item $cbor = $cbor->forbid_objects ([$enable])
		257
		258	=item $enabled = $cbor->get_forbid_objects
		259
		260	Disables the use of the object serialiser protocol.
		261
		262	If C<$enable> is true (or missing), then C<encode> will will throw an
		263	exception when it encounters perl objects that would be encoded using the
		264	perl-object tag (26). When C<decode> encounters such tags, it will fall
		265	back to the general filter/tagged logic as if this were an unknown tag (by
		266	default resulting in a C<CBOR::XC::Tagged> object).
		267
		268	If C<$enable> is false (the default), then C<encode> will use the
		269	L<Types::Serialiser> object serialisation protocol to serialise objects
		270	into perl-object tags, and C<decode> will do the same to decode such tags.
		271
		272	See L<SECURITY CONSIDERATIONS>, below, for more info on why forbidding this
		273	protocol can be useful.
		274
210	=item $cbor = $cbor->pack_strings ([$enable])	275	=item $cbor = $cbor->pack_strings ([$enable])
211		276
212	=item $enabled = $cbor->get_pack_strings	277	=item $enabled = $cbor->get_pack_strings
213		278
214	If C<$enable> is true (or missing), then C<encode> will try not to encode	279	If C<$enable> is true (or missing), then C<encode> will try not to encode
…		…
226	the standard CBOR way.	291	the standard CBOR way.
227		292
228	This option does not affect C<decode> in any way - string references will	293	This option does not affect C<decode> in any way - string references will
229	always be decoded properly if present.	294	always be decoded properly if present.
230		295
		296	=item $cbor = $cbor->text_keys ([$enable])
		297
		298	=item $enabled = $cbor->get_text_keys
		299
		300	If C<$enabled> is true (or missing), then C<encode> will encode all
		301	perl hash keys as CBOR text strings/UTF-8 string, upgrading them as needed.
		302
		303	If C<$enable> is false (the default), then C<encode> will encode hash keys
		304	normally - upgraded perl strings (strings internally encoded as UTF-8) as
		305	CBOR text strings, and downgraded perl strings as CBOR byte strings.
		306
		307	This option does not affect C<decode> in any way.
		308
		309	This option is useful for interoperability with CBOR decoders that don't
		310	treat byte strings as a form of text. It is especially useful as Perl
		311	gives very little control over hash keys.
		312
		313	Enabling this option can be slow, as all downgraded hash keys that are
		314	encoded need to be scanned and converted to UTF-8.
		315
		316	=item $cbor = $cbor->text_strings ([$enable])
		317
		318	=item $enabled = $cbor->get_text_strings
		319
		320	This option works similar to C<text_keys>, above, but works on all strings
		321	(including hash keys), so C<text_keys> has no further effect after
		322	enabling C<text_strings>.
		323
		324	If C<$enabled> is true (or missing), then C<encode> will encode all perl
		325	strings as CBOR text strings/UTF-8 strings, upgrading them as needed.
		326
		327	If C<$enable> is false (the default), then C<encode> will encode strings
		328	normally (but see C<text_keys>) - upgraded perl strings (strings
		329	internally encoded as UTF-8) as CBOR text strings, and downgraded perl
		330	strings as CBOR byte strings.
		331
		332	This option does not affect C<decode> in any way.
		333
		334	This option has similar advantages and disadvantages as C<text_keys>. In
		335	addition, this option effectively removes the ability to encode byte
		336	strings, which might break some C<FREEZE> and C<TO_CBOR> methods that rely
		337	on this, such as bignum encoding, so this option is mainly useful for very
		338	simple data.
		339
		340	=item $cbor = $cbor->validate_utf8 ([$enable])
		341
		342	=item $enabled = $cbor->get_validate_utf8
		343
		344	If C<$enable> is true (or missing), then C<decode> will validate that
		345	elements (text strings) containing UTF-8 data in fact contain valid UTF-8
		346	data (instead of blindly accepting it). This validation obviously takes
		347	extra time during decoding.
		348
		349	The concept of "valid UTF-8" used is perl's concept, which is a superset
		350	of the official UTF-8.
		351
		352	If C<$enable> is false (the default), then C<decode> will blindly accept
		353	UTF-8 data, marking them as valid UTF-8 in the resulting data structure
		354	regardless of whether that's true or not.
		355
		356	Perl isn't too happy about corrupted UTF-8 in strings, but should
		357	generally not crash or do similarly evil things. Extensions might be not
		358	so forgiving, so it's recommended to turn on this setting if you receive
		359	untrusted CBOR.
		360
		361	This option does not affect C<encode> in any way - strings that are
		362	supposedly valid UTF-8 will simply be dumped into the resulting CBOR
		363	string without checking whether that is, in fact, true or not.
		364
231	=item $cbor = $cbor->filter ([$cb->($tag, $value)])	365	=item $cbor = $cbor->filter ([$cb->($tag, $value)])
232		366
233	=item $cb_or_undef = $cbor->get_filter	367	=item $cb_or_undef = $cbor->get_filter
234		368
235	Sets or replaces the tagged value decoding filter (when C<$cb> is	369	Sets or replaces the tagged value decoding filter (when C<$cb> is
…		…
247	replace the tagged value in the decoded data structure, or no values,	381	replace the tagged value in the decoded data structure, or no values,
248	which will result in default handling, which currently means the decoder	382	which will result in default handling, which currently means the decoder
249	creates a C<CBOR::XS::Tagged> object to hold the tag and the value.	383	creates a C<CBOR::XS::Tagged> object to hold the tag and the value.
250		384
251	When the filter is cleared (the default state), the default filter	385	When the filter is cleared (the default state), the default filter
252	function, C<CBOR::XS::default_filter>, is used. This function simply looks	386	function, C<CBOR::XS::default_filter>, is used. This function simply
253	up the tag in the C<%CBOR::XS::FILTER> hash. If an entry exists it must be	387	looks up the tag in the C<%CBOR::XS::FILTER> hash. If an entry exists
254	a code reference that is called with tag and value, and is responsible for	388	it must be a code reference that is called with tag and value, and is
255	decoding the value. If no entry exists, it returns no values.	389	responsible for decoding the value. If no entry exists, it returns no
		390	values. C<CBOR::XS> provides a number of default filter functions already,
		391	the the C<%CBOR::XS::FILTER> hash can be freely extended with more.
		392
		393	C<CBOR::XS> additionally provides an alternative filter function that is
		394	supposed to be safe to use with untrusted data (which the default filter
		395	might not), called C<CBOR::XS::safe_filter>, which works the same as
		396	the C<default_filter> but uses the C<%CBOR::XS::SAFE_FILTER> variable
		397	instead. It is prepopulated with the tag decoding functions that are
		398	deemed safe (basically the same as C<%CBOR::XS::FILTER> without all
		399	the bignum tags), and can be extended by user code as wlel, although,
		400	obviously, one should be very careful about adding decoding functions
		401	here, since the expectation is that they are safe to use on untrusted
		402	data, after all.
256		403
257	Example: decode all tags not handled internally into C<CBOR::XS::Tagged>	404	Example: decode all tags not handled internally into C<CBOR::XS::Tagged>
258	objects, with no other special handling (useful when working with	405	objects, with no other special handling (useful when working with
259	potentially "unsafe" CBOR data).	406	potentially "unsafe" CBOR data).
260		407
…		…
267	my ($tag, $value);	414	my ($tag, $value);
268		415
269	"tag 1347375694 value $value"	416	"tag 1347375694 value $value"
270	};	417	};
271		418
		419	Example: provide your own filter function that looks up tags in your own
		420	hash:
		421
		422	my %my_filter = (
		423	998347484 => sub {
		424	my ($tag, $value);
		425
		426	"tag 998347484 value $value"
		427	};
		428	);
		429
		430	my $coder = CBOR::XS->new->filter (sub {
		431	&{ $my_filter{$_[0]} or return }
		432	});
		433
		434
		435	Example: use the safe filter function (see L<SECURITY CONSIDERATIONS> for
		436	more considerations on security).
		437
		438	CBOR::XS->new->filter (\&CBOR::XS::safe_filter)->decode ($cbor_data);
		439
272	=item $cbor_data = $cbor->encode ($perl_scalar)	440	=item $cbor_data = $cbor->encode ($perl_scalar)
273		441
274	Converts the given Perl data structure (a scalar value) to its CBOR	442	Converts the given Perl data structure (a scalar value) to its CBOR
275	representation.	443	representation.
276		444
…		…
289	and you need to know where the first CBOR string ends amd the next one	457	and you need to know where the first CBOR string ends amd the next one
290	starts.	458	starts.
291		459
292	CBOR::XS->new->decode_prefix ("......")	460	CBOR::XS->new->decode_prefix ("......")
293	=> ("...", 3)	461	=> ("...", 3)
		462
		463	=back
		464
		465	=head2 INCREMENTAL PARSING
		466
		467	In some cases, there is the need for incremental parsing of JSON
		468	texts. While this module always has to keep both CBOR text and resulting
		469	Perl data structure in memory at one time, it does allow you to parse a
		470	CBOR stream incrementally, using a similar to using "decode_prefix" to see
		471	if a full CBOR object is available, but is much more efficient.
		472
		473	It basically works by parsing as much of a CBOR string as possible - if
		474	the CBOR data is not complete yet, the pasrer will remember where it was,
		475	to be able to restart when more data has been accumulated. Once enough
		476	data is available to either decode a complete CBOR value or raise an
		477	error, a real decode will be attempted.
		478
		479	A typical use case would be a network protocol that consists of sending
		480	and receiving CBOR-encoded messages. The solution that works with CBOR and
		481	about anything else is by prepending a length to every CBOR value, so the
		482	receiver knows how many octets to read. More compact (and slightly slower)
		483	would be to just send CBOR values back-to-back, as C<CBOR::XS> knows where
		484	a CBOR value ends, and doesn't need an explicit length.
		485
		486	The following methods help with this:
		487
		488	=over 4
		489
		490	=item @decoded = $cbor->incr_parse ($buffer)
		491
		492	This method attempts to decode exactly one CBOR value from the beginning
		493	of the given C<$buffer>. The value is removed from the C<$buffer> on
		494	success. When C<$buffer> doesn't contain a complete value yet, it returns
		495	nothing. Finally, when the C<$buffer> doesn't start with something
		496	that could ever be a valid CBOR value, it raises an exception, just as
		497	C<decode> would. In the latter case the decoder state is undefined and
		498	must be reset before being able to parse further.
		499
		500	This method modifies the C<$buffer> in place. When no CBOR value can be
		501	decoded, the decoder stores the current string offset. On the next call,
		502	continues decoding at the place where it stopped before. For this to make
		503	sense, the C<$buffer> must begin with the same octets as on previous
		504	unsuccessful calls.
		505
		506	You can call this method in scalar context, in which case it either
		507	returns a decoded value or C<undef>. This makes it impossible to
		508	distinguish between CBOR null values (which decode to C<undef>) and an
		509	unsuccessful decode, which is often acceptable.
		510
		511	=item @decoded = $cbor->incr_parse_multiple ($buffer)
		512
		513	Same as C<incr_parse>, but attempts to decode as many CBOR values as
		514	possible in one go, instead of at most one. Calls to C<incr_parse> and
		515	C<incr_parse_multiple> can be interleaved.
		516
		517	=item $cbor->incr_reset
		518
		519	Resets the incremental decoder. This throws away any saved state, so that
		520	subsequent calls to C<incr_parse> or C<incr_parse_multiple> start to parse
		521	a new CBOR value from the beginning of the C<$buffer> again.
		522
		523	This method can be called at any time, but it I<must> be called if you want
		524	to change your C<$buffer> or there was a decoding error and you want to
		525	reuse the C<$cbor> object for future incremental parsings.
294		526
295	=back	527	=back
296		528
297		529
298	=head1 MAPPING	530	=head1 MAPPING
…		…
371		603
372	=item hash references	604	=item hash references
373		605
374	Perl hash references become CBOR maps. As there is no inherent ordering in	606	Perl hash references become CBOR maps. As there is no inherent ordering in
375	hash keys (or CBOR maps), they will usually be encoded in a pseudo-random	607	hash keys (or CBOR maps), they will usually be encoded in a pseudo-random
376	order. This order can be different each time a hahs is encoded.	608	order. This order can be different each time a hash is encoded.
377		609
378	Currently, tied hashes will use the indefinite-length format, while normal	610	Currently, tied hashes will use the indefinite-length format, while normal
379	hashes will use the fixed-length format.	611	hashes will use the fixed-length format.
380		612
381	=item array references	613	=item array references
…		…
434	my $x = 3.1; # some variable containing a number	666	my $x = 3.1; # some variable containing a number
435	"$x"; # stringified	667	"$x"; # stringified
436	$x .= ""; # another, more awkward way to stringify	668	$x .= ""; # another, more awkward way to stringify
437	print $x; # perl does it for you, too, quite often	669	print $x; # perl does it for you, too, quite often
438		670
439	You can force whether a string ie encoded as byte or text string by using	671	You can force whether a string is encoded as byte or text string by using
440	C<utf8::upgrade> and C<utf8::downgrade>):	672	C<utf8::upgrade> and C<utf8::downgrade> (if C<text_strings> is disabled):
441		673
442	utf8::upgrade $x; # encode $x as text string	674	utf8::upgrade $x; # encode $x as text string
443	utf8::downgrade $x; # encode $x as byte string	675	utf8::downgrade $x; # encode $x as byte string
444		676
445	Perl doesn't define what operations up- and downgrade strings, so if the	677	Perl doesn't define what operations up- and downgrade strings, so if the
446	difference between byte and text is important, you should up- or downgrade	678	difference between byte and text is important, you should up- or downgrade
447	your string as late as possible before encoding.	679	your string as late as possible before encoding. You can also force the
		680	use of CBOR text strings by using C<text_keys> or C<text_strings>.
448		681
449	You can force the type to be a CBOR number by numifying it:	682	You can force the type to be a CBOR number by numifying it:
450		683
451	my $x = "3"; # some variable containing a string	684	my $x = "3"; # some variable containing a string
452	$x += 0; # numify it, ensuring it will be dumped as a number	685	$x += 0; # numify it, ensuring it will be dumped as a number
…		…
465		698
466	=back	699	=back
467		700
468	=head2 OBJECT SERIALISATION	701	=head2 OBJECT SERIALISATION
469		702
		703	This module implements both a CBOR-specific and the generic
		704	L<Types::Serialier> object serialisation protocol. The following
		705	subsections explain both methods.
		706
		707	=head3 ENCODING
		708
470	This module knows two way to serialise a Perl object: The CBOR-specific	709	This module knows two way to serialise a Perl object: The CBOR-specific
471	way, and the generic way.	710	way, and the generic way.
472		711
473	Whenever the encoder encounters a Perl object that it cnanot serialise	712	Whenever the encoder encounters a Perl object that it cannot serialise
474	directly (most of them), it will first look up the C<TO_CBOR> method on	713	directly (most of them), it will first look up the C<TO_CBOR> method on
475	it.	714	it.
476		715
477	If it has a C<TO_CBOR> method, it will call it with the object as only	716	If it has a C<TO_CBOR> method, it will call it with the object as only
478	argument, and expects exactly one return value, which it will then	717	argument, and expects exactly one return value, which it will then
…		…
484		723
485	The C<FREEZE> method can return any number of values (i.e. zero or	724	The C<FREEZE> method can return any number of values (i.e. zero or
486	more). These will be encoded as CBOR perl object, together with the	725	more). These will be encoded as CBOR perl object, together with the
487	classname.	726	classname.
488		727
		728	These methods I<MUST NOT> change the data structure that is being
		729	serialised. Failure to comply to this can result in memory corruption -
		730	and worse.
		731
489	If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail	732	If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail
490	with an error.	733	with an error.
491		734
		735	=head3 DECODING
		736
492	Objects encoded via C<TO_CBOR> cannot be automatically decoded, but	737	Objects encoded via C<TO_CBOR> cannot (normally) be automatically decoded,
493	objects encoded via C<FREEZE> can be decoded using the following protocol:	738	but objects encoded via C<FREEZE> can be decoded using the following
		739	protocol:
494		740
495	When an encoded CBOR perl object is encountered by the decoder, it will	741	When an encoded CBOR perl object is encountered by the decoder, it will
496	look up the C<THAW> method, by using the stored classname, and will fail	742	look up the C<THAW> method, by using the stored classname, and will fail
497	if the method cannot be found.	743	if the method cannot be found.
498		744
499	After the lookup it will call the C<THAW> method with the stored classname	745	After the lookup it will call the C<THAW> method with the stored classname
500	as first argument, the constant string C<CBOR> as second argument, and all	746	as first argument, the constant string C<CBOR> as second argument, and all
501	values returned by C<FREEZE> as remaining arguments.	747	values returned by C<FREEZE> as remaining arguments.
502		748
503	=head4 EXAMPLES	749	=head3 EXAMPLES
504		750
505	Here is an example C<TO_CBOR> method:	751	Here is an example C<TO_CBOR> method:
506		752
507	sub My::Object::TO_CBOR {	753	sub My::Object::TO_CBOR {
508	my ($obj) = @_;	754	my ($obj) = @_;
…		…
540	"$self" # encode url string	786	"$self" # encode url string
541	}	787	}
542		788
543	sub URI::THAW {	789	sub URI::THAW {
544	my ($class, $serialiser, $uri) = @_;	790	my ($class, $serialiser, $uri) = @_;
545
546	$class->new ($uri)	791	$class->new ($uri)
547	}	792	}
548		793
549	Unlike C<TO_CBOR>, multiple values can be returned by C<FREEZE>. For	794	Unlike C<TO_CBOR>, multiple values can be returned by C<FREEZE>. For
550	example, a C<FREEZE> method that returns "type", "id" and "variant" values	795	example, a C<FREEZE> method that returns "type", "id" and "variant" values
…		…
681	additional tags (such as base64url).	926	additional tags (such as base64url).
682		927
683	=head2 ENFORCED TAGS	928	=head2 ENFORCED TAGS
684		929
685	These tags are always handled when decoding, and their handling cannot be	930	These tags are always handled when decoding, and their handling cannot be
686	overriden by the user.	931	overridden by the user.
687		932
688	=over 4	933	=over 4
689		934
690	=item 26 (perl-object, L<http://cbor.schmorp.de/perl-object>)	935	=item 26 (perl-object, L<http://cbor.schmorp.de/perl-object>)
691		936
692	These tags are automatically created (and decoded) for serialisable	937	These tags are automatically created (and decoded) for serialisable
693	objects using the C<FREEZE/THAW> methods (the L<Types::Serialier> object	938	objects using the C<FREEZE/THAW> methods (the L<Types::Serialier> object
694	serialisation protocol). See L<OBJECT SERIALISATION> for details.	939	serialisation protocol). See L<OBJECT SERIALISATION> for details.
695		940
696	=item 28, 29 (sharable, sharedref, L <http://cbor.schmorp.de/value-sharing>)	941	=item 28, 29 (shareable, sharedref, L<http://cbor.schmorp.de/value-sharing>)
697		942
698	These tags are automatically decoded when encountered, resulting in	943	These tags are automatically decoded when encountered (and they do not
		944	result in a cyclic data structure, see C<allow_cycles>), resulting in
699	shared values in the decoded object. They are only encoded, however, when	945	shared values in the decoded object. They are only encoded, however, when
700	C<allow_sharable> is enabled.	946	C<allow_sharing> is enabled.
701		947
		948	Not all shared values can be successfully decoded: values that reference
		949	themselves will I<currently> decode as C<undef> (this is not the same
		950	as a reference pointing to itself, which will be represented as a value
		951	that contains an indirect reference to itself - these will be decoded
		952	properly).
		953
		954	Note that considerably more shared value data structures can be decoded
		955	than will be encoded - currently, only values pointed to by references
		956	will be shared, others will not. While non-reference shared values can be
		957	generated in Perl with some effort, they were considered too unimportant
		958	to be supported in the encoder. The decoder, however, will decode these
		959	values as shared values.
		960
702	=item 256, 25 (stringref-namespace, stringref, L <http://cbor.schmorp.de/stringref>)	961	=item 256, 25 (stringref-namespace, stringref, L<http://cbor.schmorp.de/stringref>)
703		962
704	These tags are automatically decoded when encountered. They are only	963	These tags are automatically decoded when encountered. They are only
705	encoded, however, when C<pack_strings> is enabled.	964	encoded, however, when C<pack_strings> is enabled.
706		965
707	=item 22098 (indirection, L<http://cbor.schmorp.de/indirection>)	966	=item 22098 (indirection, L<http://cbor.schmorp.de/indirection>)
708		967
709	This tag is automatically generated when a reference are encountered (with	968	This tag is automatically generated when a reference are encountered (with
710	the exception of hash and array refernces). It is converted to a reference	969	the exception of hash and array references). It is converted to a reference
711	when decoding.	970	when decoding.
712		971
713	=item 55799 (self-describe CBOR, RFC 7049)	972	=item 55799 (self-describe CBOR, RFC 7049)
714		973
715	This value is not generated on encoding (unless explicitly requested by	974	This value is not generated on encoding (unless explicitly requested by
…		…
718	=back	977	=back
719		978
720	=head2 NON-ENFORCED TAGS	979	=head2 NON-ENFORCED TAGS
721		980
722	These tags have default filters provided when decoding. Their handling can	981	These tags have default filters provided when decoding. Their handling can
723	be overriden by changing the C<%CBOR::XS::FILTER> entry for the tag, or by	982	be overridden by changing the C<%CBOR::XS::FILTER> entry for the tag, or by
724	providing a custom C<filter> callback when decoding.	983	providing a custom C<filter> callback when decoding.
725		984
726	When they result in decoding into a specific Perl class, the module	985	When they result in decoding into a specific Perl class, the module
727	usually provides a corresponding C<TO_CBOR> method as well.	986	usually provides a corresponding C<TO_CBOR> method as well.
728		987
…		…
731	provide these modules. The decoding usually fails with an exception if the	990	provide these modules. The decoding usually fails with an exception if the
732	required module cannot be loaded.	991	required module cannot be loaded.
733		992
734	=over 4	993	=over 4
735		994
		995	=item 0, 1 (date/time string, seconds since the epoch)
		996
		997	These tags are decoded into L<Time::Piece> objects. The corresponding
		998	C<Time::Piece::TO_CBOR> method always encodes into tag 1 values currently.
		999
		1000	The L<Time::Piece> API is generally surprisingly bad, and fractional
		1001	seconds are only accidentally kept intact, so watch out. On the plus side,
		1002	the module comes with perl since 5.10, which has to count for something.
		1003
736	=item 2, 3 (positive/negative bignum)	1004	=item 2, 3 (positive/negative bignum)
737		1005
738	These tags are decoded into L<Math::BigInt> objects. The corresponding	1006	These tags are decoded into L<Math::BigInt> objects. The corresponding
739	C<Math::BigInt::TO_CBOR> method encodes "small" bigints into normal CBOR	1007	C<Math::BigInt::TO_CBOR> method encodes "small" bigints into normal CBOR
740	integers, and others into positive/negative CBOR bignums.	1008	integers, and others into positive/negative CBOR bignums.
741		1009
742	=item 4, 5 (decimal fraction/bigfloat)	1010	=item 4, 5, 264, 265 (decimal fraction/bigfloat)
743		1011
744	Both decimal fractions and bigfloats are decoded into L<Math::BigFloat>	1012	Both decimal fractions and bigfloats are decoded into L<Math::BigFloat>
745	objects. The corresponding C<Math::BigFloat::TO_CBOR> method I<always>	1013	objects. The corresponding C<Math::BigFloat::TO_CBOR> method I<always>
746	encodes into a decimal fraction.	1014	encodes into a decimal fraction (either tag 4 or 264).
747		1015
748	CBOR cannot represent bigfloats with I<very> large exponents - conversion	1016	NaN and infinities are not encoded properly, as they cannot be represented
749	of such big float objects is undefined.	1017	in CBOR.
750		1018
751	Also, NaN and infinities are not encoded properly.	1019	See L<BIGNUM SECURITY CONSIDERATIONS> for more info.
		1020
		1021	=item 30 (rational numbers)
		1022
		1023	These tags are decoded into L<Math::BigRat> objects. The corresponding
		1024	C<Math::BigRat::TO_CBOR> method encodes rational numbers with denominator
		1025	C<1> via their numerator only, i.e., they become normal integers or
		1026	C<bignums>.
		1027
		1028	See L<BIGNUM SECURITY CONSIDERATIONS> for more info.
752		1029
753	=item 21, 22, 23 (expected later JSON conversion)	1030	=item 21, 22, 23 (expected later JSON conversion)
754		1031
755	CBOR::XS is not a CBOR-to-JSON converter, and will simply ignore these	1032	CBOR::XS is not a CBOR-to-JSON converter, and will simply ignore these
756	tags.	1033	tags.
…		…
761	C<URI::TO_CBOR> method again results in a CBOR URI value.	1038	C<URI::TO_CBOR> method again results in a CBOR URI value.
762		1039
763	=back	1040	=back
764		1041
765	=cut	1042	=cut
766
767	our %FILTER = (
768	# 0 # rfc4287 datetime, utf-8
769	# 1 # unix timestamp, any
770
771	2 => sub { # pos bigint
772	require Math::BigInt;
773	Math::BigInt->new ("0x" . unpack "H*", pop)
774	},
775
776	3 => sub { # neg bigint
777	require Math::BigInt;
778	-Math::BigInt->new ("0x" . unpack "H*", pop)
779	},
780
781	4 => sub { # decimal fraction, array
782	require Math::BigFloat;
783	Math::BigFloat->new ($_[1][1] . "E" . $_[1][0])
784	},
785
786	5 => sub { # bigfloat, array
787	require Math::BigFloat;
788	scalar Math::BigFloat->new ($_[1][1])->blsft ($_[1][0], 2)
789	},
790
791	21 => sub { pop }, # expected conversion to base64url encoding
792	22 => sub { pop }, # expected conversion to base64 encoding
793	23 => sub { pop }, # expected conversion to base16 encoding
794
795	# 24 # embedded cbor, byte string
796
797	32 => sub {
798	require URI;
799	URI->new (pop)
800	},
801
802	# 33 # base64url rfc4648, utf-8
803	# 34 # base64 rfc46484, utf-8
804	# 35 # regex pcre/ecma262, utf-8
805	# 36 # mime message rfc2045, utf-8
806	);
807
808		1043
809	=head1 CBOR and JSON	1044	=head1 CBOR and JSON
810		1045
811	CBOR is supposed to implement a superset of the JSON data model, and is,	1046	CBOR is supposed to implement a superset of the JSON data model, and is,
812	with some coercion, able to represent all JSON texts (something that other	1047	with some coercion, able to represent all JSON texts (something that other
…		…
821	CBOR intact.	1056	CBOR intact.
822		1057
823		1058
824	=head1 SECURITY CONSIDERATIONS	1059	=head1 SECURITY CONSIDERATIONS
825		1060
826	When you are using CBOR in a protocol, talking to untrusted potentially	1061	Tl;dr... if you want to decode or encode CBOR from untrusted sources, you
827	hostile creatures requires relatively few measures.	1062	should start with a coder object created via C<new_safe>:
828		1063
		1064	my $coder = CBOR::XS->new_safe;
		1065
		1066	my $data = $coder->decode ($cbor_text);
		1067	my $cbor = $coder->encode ($data);
		1068
		1069	Longer version: When you are using CBOR in a protocol, talking to
		1070	untrusted potentially hostile creatures requires some thought:
		1071
		1072	=over 4
		1073
		1074	=item Security of the CBOR decoder itself
		1075
829	First of all, your CBOR decoder should be secure, that is, should not have	1076	First and foremost, your CBOR decoder should be secure, that is, should
		1077	not have any buffer overflows or similar bugs that could potentially be
830	any buffer overflows. Obviously, this module should ensure that and I am	1078	exploited. Obviously, this module should ensure that and I am trying hard
831	trying hard on making that true, but you never know.	1079	on making that true, but you never know.
832		1080
		1081	=item CBOR::XS can invoke almost arbitrary callbacks during decoding
		1082
		1083	CBOR::XS supports object serialisation - decoding CBOR can cause calls
		1084	to I<any> C<THAW> method in I<any> package that exists in your process
		1085	(that is, CBOR::XS will not try to load modules, but any existing C<THAW>
		1086	method or function can be called, so they all have to be secure).
		1087
		1088	Less obviously, it will also invoke C<TO_CBOR> and C<FREEZE> methods -
		1089	even if all your C<THAW> methods are secure, encoding data structures from
		1090	untrusted sources can invoke those and trigger bugs in those.
		1091
		1092	So, if you are not sure about the security of all the modules you
		1093	have loaded (you shouldn't), you should disable this part using
		1094	C<forbid_objects>.
		1095
		1096	=item CBOR can be extended with tags that call library code
		1097
		1098	CBOR can be extended with tags, and C<CBOR::XS> has a registry of
		1099	conversion functions for many existing tags that can be extended via
		1100	third-party modules (see the C<filter> method).
		1101
		1102	If you don't trust these, you should configure the "safe" filter function,
		1103	C<CBOR::XS::safe_filter>, which by default only includes conversion
		1104	functions that are considered "safe" by the author (but again, they can be
		1105	extended by third party modules).
		1106
		1107	Depending on your level of paranoia, you can use the "safe" filter:
		1108
		1109	$cbor->filter (\&CBOR::XS::safe_filter);
		1110
		1111	... your own filter...
		1112
		1113	$cbor->filter (sub { ... do your stuffs here ... });
		1114
		1115	... or even no filter at all, disabling all tag decoding:
		1116
		1117	$cbor->filter (sub { });
		1118
		1119	This is never a problem for encoding, as the tag mechanism only exists in
		1120	CBOR texts.
		1121
		1122	=item Resource-starving attacks: object memory usage
		1123
833	Second, you need to avoid resource-starving attacks. That means you should	1124	You need to avoid resource-starving attacks. That means you should limit
834	limit the size of CBOR data you accept, or make sure then when your	1125	the size of CBOR data you accept, or make sure then when your resources
835	resources run out, that's just fine (e.g. by using a separate process that	1126	run out, that's just fine (e.g. by using a separate process that can
836	can crash safely). The size of a CBOR string in octets is usually a good	1127	crash safely). The size of a CBOR string in octets is usually a good
837	indication of the size of the resources required to decode it into a Perl	1128	indication of the size of the resources required to decode it into a Perl
838	structure. While CBOR::XS can check the size of the CBOR text, it might be	1129	structure. While CBOR::XS can check the size of the CBOR text (using
839	too late when you already have it in memory, so you might want to check	1130	C<max_size>), it might be too late when you already have it in memory, so
840	the size before you accept the string.	1131	you might want to check the size before you accept the string.
841		1132
		1133	As for encoding, it is possible to construct data structures that are
		1134	relatively small but result in large CBOR texts (for example by having an
		1135	array full of references to the same big data structure, which will all be
		1136	deep-cloned during encoding by default). This is rarely an actual issue
		1137	(and the worst case is still just running out of memory), but you can
		1138	reduce this risk by using C<allow_sharing>.
		1139
		1140	=item Resource-starving attacks: stack overflows
		1141
842	Third, CBOR::XS recurses using the C stack when decoding objects and	1142	CBOR::XS recurses using the C stack when decoding objects and arrays. The
843	arrays. The C stack is a limited resource: for instance, on my amd64	1143	C stack is a limited resource: for instance, on my amd64 machine with 8MB
844	machine with 8MB of stack size I can decode around 180k nested arrays but	1144	of stack size I can decode around 180k nested arrays but only 14k nested
845	only 14k nested CBOR objects (due to perl itself recursing deeply on croak	1145	CBOR objects (due to perl itself recursing deeply on croak to free the
846	to free the temporary). If that is exceeded, the program crashes. To be	1146	temporary). If that is exceeded, the program crashes. To be conservative,
847	conservative, the default nesting limit is set to 512. If your process	1147	the default nesting limit is set to 512. If your process has a smaller
848	has a smaller stack, you should adjust this setting accordingly with the	1148	stack, you should adjust this setting accordingly with the C<max_depth>
849	C<max_depth> method.	1149	method.
		1150
		1151	=item Resource-starving attacks: CPU en-/decoding complexity
		1152
		1153	CBOR::XS will use the L<Math::BigInt>, L<Math::BigFloat> and
		1154	L<Math::BigRat> libraries to represent encode/decode bignums. These can
		1155	be very slow (as in, centuries of CPU time) and can even crash your
		1156	program (and are generally not very trustworthy). See the next section for
		1157	details.
		1158
		1159	=item Data breaches: leaking information in error messages
		1160
		1161	CBOR::XS might leak contents of your Perl data structures in its error
		1162	messages, so when you serialise sensitive information you might want to
		1163	make sure that exceptions thrown by CBOR::XS will not end up in front of
		1164	untrusted eyes.
		1165
		1166	=item Something else...
850		1167
851	Something else could bomb you, too, that I forgot to think of. In that	1168	Something else could bomb you, too, that I forgot to think of. In that
852	case, you get to keep the pieces. I am always open for hints, though...	1169	case, you get to keep the pieces. I am always open for hints, though...
853		1170
854	Also keep in mind that CBOR::XS might leak contents of your Perl data	1171	=back
855	structures in its error messages, so when you serialise sensitive	1172
856	information you might want to make sure that exceptions thrown by CBOR::XS	1173
857	will not end up in front of untrusted eyes.	1174	=head1 BIGNUM SECURITY CONSIDERATIONS
		1175
		1176	CBOR::XS provides a C<TO_CBOR> method for both L<Math::BigInt> and
		1177	L<Math::BigFloat> that tries to encode the number in the simplest possible
		1178	way, that is, either a CBOR integer, a CBOR bigint/decimal fraction (tag
		1179	4) or an arbitrary-exponent decimal fraction (tag 264). Rational numbers
		1180	(L<Math::BigRat>, tag 30) can also contain bignums as members.
		1181
		1182	CBOR::XS will also understand base-2 bigfloat or arbitrary-exponent
		1183	bigfloats (tags 5 and 265), but it will never generate these on its own.
		1184
		1185	Using the built-in L<Math::BigInt::Calc> support, encoding and decoding
		1186	decimal fractions is generally fast. Decoding bigints can be slow for very
		1187	big numbers (tens of thousands of digits, something that could potentially
		1188	be caught by limiting the size of CBOR texts), and decoding bigfloats or
		1189	arbitrary-exponent bigfloats can be I<extremely> slow (minutes, decades)
		1190	for large exponents (roughly 40 bit and longer).
		1191
		1192	Additionally, L<Math::BigInt> can take advantage of other bignum
		1193	libraries, such as L<Math::GMP>, which cannot handle big floats with large
		1194	exponents, and might simply abort or crash your program, due to their code
		1195	quality.
		1196
		1197	This can be a concern if you want to parse untrusted CBOR. If it is, you
		1198	might want to disable decoding of tag 2 (bigint) and 3 (negative bigint)
		1199	types. You should also disable types 5 and 265, as these can be slow even
		1200	without bigints.
		1201
		1202	Disabling bigints will also partially or fully disable types that rely on
		1203	them, e.g. rational numbers that use bignums.
		1204
858		1205
859	=head1 CBOR IMPLEMENTATION NOTES	1206	=head1 CBOR IMPLEMENTATION NOTES
860		1207
861	This section contains some random implementation notes. They do not	1208	This section contains some random implementation notes. They do not
862	describe guaranteed behaviour, but merely behaviour as-is implemented	1209	describe guaranteed behaviour, but merely behaviour as-is implemented
…		…
871	Only the double data type is supported for NV data types - when Perl uses	1218	Only the double data type is supported for NV data types - when Perl uses
872	long double to represent floating point values, they might not be encoded	1219	long double to represent floating point values, they might not be encoded
873	properly. Half precision types are accepted, but not encoded.	1220	properly. Half precision types are accepted, but not encoded.
874		1221
875	Strict mode and canonical mode are not implemented.	1222	Strict mode and canonical mode are not implemented.
		1223
		1224
		1225	=head1 LIMITATIONS ON PERLS WITHOUT 64-BIT INTEGER SUPPORT
		1226
		1227	On perls that were built without 64 bit integer support (these are rare
		1228	nowadays, even on 32 bit architectures, as all major Perl distributions
		1229	are built with 64 bit integer support), support for any kind of 64 bit
		1230	integer in CBOR is very limited - most likely, these 64 bit values will
		1231	be truncated, corrupted, or otherwise not decoded correctly. This also
		1232	includes string, array and map sizes that are stored as 64 bit integers.
876		1233
877		1234
878	=head1 THREADS	1235	=head1 THREADS
879		1236
880	This module is I<not> guaranteed to be thread safe and there are no	1237	This module is I<not> guaranteed to be thread safe and there are no
…		…
894	Please refrain from using rt.cpan.org or any other bug reporting	1251	Please refrain from using rt.cpan.org or any other bug reporting
895	service. I put the contact address into my modules for a reason.	1252	service. I put the contact address into my modules for a reason.
896		1253
897	=cut	1254	=cut
898		1255
		1256	# clumsy and slow hv_store-in-hash helper function
		1257	sub _hv_store {
		1258	$_[0]{$_[1]} = $_[2];
		1259	}
		1260
899	our %FILTER = (	1261	our %FILTER = (
900	# 0 # rfc4287 datetime, utf-8	1262	0 => sub { # rfc4287 datetime, utf-8
901	# 1 # unix timestamp, any	1263	require Time::Piece;
		1264	# Time::Piece::Strptime uses the "incredibly flexible date parsing routine"
		1265	# from FreeBSD, which can't parse ISO 8601, RFC3339, RFC4287 or much of anything
		1266	# else either. Whats incredibe over standard strptime totally escapes me.
		1267	# doesn't do fractional times, either. sigh.
		1268	# In fact, it's all a lie, it uses whatever strptime it wants, and of course,
		1269	# they are all incompatible. The openbsd one simply ignores %z (but according to the
		1270	# docs, it would be much more incredibly flexible indeed. If it worked, that is.).
		1271	scalar eval {
		1272	my $s = $_[1];
		1273
		1274	$s =~ s/Z$/+00:00/;
		1275	$s =~ s/(\.[0-9]+)?([+-][0-9][0-9]):([0-9][0-9])$//
		1276	or die;
		1277
		1278	my $b = $1 - ($2 * 60 + $3) * 60; # fractional part + offset. hopefully
		1279	my $d = Time::Piece->strptime ($s, "%Y-%m-%dT%H:%M:%S");
		1280
		1281	Time::Piece::gmtime ($d->epoch + $b)
		1282	} \|\| die "corrupted CBOR date/time string ($_[0])";
		1283	},
		1284
		1285	1 => sub { # seconds since the epoch, possibly fractional
		1286	require Time::Piece;
		1287	scalar Time::Piece::gmtime (pop)
		1288	},
902		1289
903	2 => sub { # pos bigint	1290	2 => sub { # pos bigint
904	require Math::BigInt;	1291	require Math::BigInt;
905	Math::BigInt->new ("0x" . unpack "H*", pop)	1292	Math::BigInt->new ("0x" . unpack "H*", pop)
906	},	1293	},
…		…
913	4 => sub { # decimal fraction, array	1300	4 => sub { # decimal fraction, array
914	require Math::BigFloat;	1301	require Math::BigFloat;
915	Math::BigFloat->new ($_[1][1] . "E" . $_[1][0])	1302	Math::BigFloat->new ($_[1][1] . "E" . $_[1][0])
916	},	1303	},
917		1304
		1305	264 => sub { # decimal fraction with arbitrary exponent
		1306	require Math::BigFloat;
		1307	Math::BigFloat->new ($_[1][1] . "E" . $_[1][0])
		1308	},
		1309
918	5 => sub { # bigfloat, array	1310	5 => sub { # bigfloat, array
919	require Math::BigFloat;	1311	require Math::BigFloat;
920	scalar Math::BigFloat->new ($_[1][1])->blsft ($_[1][0], 2)	1312	scalar Math::BigFloat->new ($_[1][1]) * Math::BigFloat->new (2)->bpow ($_[1][0])
		1313	},
		1314
		1315	265 => sub { # bigfloat with arbitrary exponent
		1316	require Math::BigFloat;
		1317	scalar Math::BigFloat->new ($_[1][1]) * Math::BigFloat->new (2)->bpow ($_[1][0])
		1318	},
		1319
		1320	30 => sub { # rational number
		1321	require Math::BigRat;
		1322	Math::BigRat->new ("$_[1][0]/$_[1][1]") # separate parameters only work in recent versons
921	},	1323	},
922		1324
923	21 => sub { pop }, # expected conversion to base64url encoding	1325	21 => sub { pop }, # expected conversion to base64url encoding
924	22 => sub { pop }, # expected conversion to base64 encoding	1326	22 => sub { pop }, # expected conversion to base64 encoding
925	23 => sub { pop }, # expected conversion to base16 encoding	1327	23 => sub { pop }, # expected conversion to base16 encoding
…		…
935	# 34 # base64 rfc46484, utf-8	1337	# 34 # base64 rfc46484, utf-8
936	# 35 # regex pcre/ecma262, utf-8	1338	# 35 # regex pcre/ecma262, utf-8
937	# 36 # mime message rfc2045, utf-8	1339	# 36 # mime message rfc2045, utf-8
938	);	1340	);
939		1341
940	sub CBOR::XS::default_filter {	1342	sub default_filter {
941	&{ $FILTER{$_[0]} or return }	1343	&{ $FILTER{$_[0]} or return }
		1344	}
		1345
		1346	our %SAFE_FILTER = map { $_ => $FILTER{$_} } 0, 1, 21, 22, 23, 32;
		1347
		1348	sub safe_filter {
		1349	&{ $SAFE_FILTER{$_[0]} or return }
942	}	1350	}
943		1351
944	sub URI::TO_CBOR {	1352	sub URI::TO_CBOR {
945	my $uri = $_[0]->as_string;	1353	my $uri = $_[0]->as_string;
946	utf8::upgrade $uri;	1354	utf8::upgrade $uri;
947	CBOR::XS::tag 32, $uri	1355	tag 32, $uri
948	}	1356	}
949		1357
950	sub Math::BigInt::TO_CBOR {	1358	sub Math::BigInt::TO_CBOR {
951	if ($_[0] >= -2147483648 && $_[0] <= 2147483647) {	1359	if (-2147483648 <= $_[0] && $_[0] <= 2147483647) {
952	$_[0]->numify	1360	$_[0]->numify
953	} else {	1361	} else {
954	my $hex = substr $_[0]->as_hex, 2;	1362	my $hex = substr $_[0]->as_hex, 2;
955	$hex = "0$hex" if 1 & length $hex; # sigh	1363	$hex = "0$hex" if 1 & length $hex; # sigh
956	CBOR::XS::tag $_[0] >= 0 ? 2 : 3, pack "H*", $hex	1364	tag $_[0] >= 0 ? 2 : 3, pack "H*", $hex
957	}	1365	}
958	}	1366	}
959		1367
960	sub Math::BigFloat::TO_CBOR {	1368	sub Math::BigFloat::TO_CBOR {
961	my ($m, $e) = $_[0]->parts;	1369	my ($m, $e) = $_[0]->parts;
		1370
		1371	-9223372036854775808 <= $e && $e <= 18446744073709551615
962	CBOR::XS::tag 4, [$e->numify, $m]	1372	? tag 4, [$e->numify, $m]
		1373	: tag 264, [$e, $m]
		1374	}
		1375
		1376	sub Math::BigRat::TO_CBOR {
		1377	my ($n, $d) = $_[0]->parts;
		1378
		1379	# older versions of BigRat need *1, as they not always return numbers
		1380
		1381	$d*1 == 1
		1382	? $n*1
		1383	: tag 30, [$n1, $d1]
		1384	}
		1385
		1386	sub Time::Piece::TO_CBOR {
		1387	tag 1, 0 + $_[0]->epoch
963	}	1388	}
964		1389
965	XSLoader::load "CBOR::XS", $VERSION;	1390	XSLoader::load "CBOR::XS", $VERSION;
966		1391
967	=head1 SEE ALSO	1392	=head1 SEE ALSO

Diff Legend

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

Comparing CBOR-XS/XS.pm (file contents): Revision 1.28 by root, Thu Nov 28 16:09:04 2013 UTC vs. Revision 1.66 by root, Tue Jun 27 02:03:24 2017 UTC

Diff Legend

Comparing CBOR-XS/XS.pm (file contents):
Revision 1.28 by root, Thu Nov 28 16:09:04 2013 UTC vs.
Revision 1.66 by root, Tue Jun 27 02:03:24 2017 UTC