--- CBOR-XS/XS.pm 2014/10/25 06:36:34 1.42 +++ CBOR-XS/XS.pm 2016/02/25 14:22:49 1.48 @@ -66,7 +66,7 @@ use common::sense; -our $VERSION = 1.26; +our $VERSION = 1.41; our @ISA = qw(Exporter); our @EXPORT = qw(encode_cbor decode_cbor); @@ -816,7 +816,7 @@ objects using the C methods (the L object serialisation protocol). See L for details. -=item 28, 29 (shareable, sharedref, L ) +=item 28, 29 (shareable, sharedref, L) These tags are automatically decoded when encountered (and they do not result in a cyclic data structure, see C), resulting in @@ -836,7 +836,7 @@ to be supported in the encoder. The decoder, however, will decode these values as shared values. -=item 256, 25 (stringref-namespace, stringref, L ) +=item 256, 25 (stringref-namespace, stringref, L) These tags are automatically decoded when encountered. They are only encoded, however, when C is enabled. @@ -1024,7 +1024,8 @@ =head1 LIMITATIONS ON PERLS WITHOUT 64-BIT INTEGER SUPPORT On perls that were built without 64 bit integer support (these are rare -nowadays, even on 32 bit architectures), support for any kind of 64 bit +nowadays, even on 32 bit architectures, as all major Perl distributions +are built with 64 bit integer support), support for any kind of 64 bit integer in CBOR is very limited - most likely, these 64 bit values will be truncated, corrupted, or otherwise not decoded correctly. This also includes string, array and map sizes that are stored as 64 bit integers. @@ -1059,7 +1060,7 @@ # else either. Whats incredibe over standard strptime totally escapes me. # doesn't do fractional times, either. sigh. # In fact, it's all a lie, it uses whatever strptime it wants, and of course, - # they are all incomptible. The openbsd one simply ignores %z (but according to the + # they are all incompatible. The openbsd one simply ignores %z (but according to the # docs, it would be much more incredibly flexible indeed. If it worked, that is.). scalar eval { my $s = $_[1];