| … | |
… | |
| 414 | use Carp (); |
414 | use Carp (); |
| 415 | |
415 | |
| 416 | our $VERSION; |
416 | our $VERSION; |
| 417 | |
417 | |
| 418 | BEGIN { |
418 | BEGIN { |
| 419 | $VERSION = 1.2; |
419 | $VERSION = 1.21; |
| 420 | XSLoader::load __PACKAGE__, $VERSION; |
420 | XSLoader::load __PACKAGE__, $VERSION; |
| 421 | } |
421 | } |
| 422 | |
422 | |
| 423 | our %EXPORT_TAGS = ( |
423 | our %EXPORT_TAGS = ( |
| 424 | const_index => [qw( |
424 | const_index => [qw( |
| … | |
… | |
| 489 | or Carp::croak "BER_TYPE_REAL NR2 value not in NR2 format ($val) (X.690 8.5.8)"; |
489 | or Carp::croak "BER_TYPE_REAL NR2 value not in NR2 format ($val) (X.690 8.5.8)"; |
| 490 | } elsif ($format == 3) { |
490 | } elsif ($format == 3) { |
| 491 | $val =~ /^ \ * [+-] (?: [0-9]+\.[0-9]* | [0-9]*\.[0-9]+ ) [eE] [+-]? [0-9]+ \z/x |
491 | $val =~ /^ \ * [+-] (?: [0-9]+\.[0-9]* | [0-9]*\.[0-9]+ ) [eE] [+-]? [0-9]+ \z/x |
| 492 | or Carp::croak "BER_TYPE_REAL NR3 value not in NR3 format ($val) (X.690 8.5.8)"; |
492 | or Carp::croak "BER_TYPE_REAL NR3 value not in NR3 format ($val) (X.690 8.5.8)"; |
| 493 | } else { |
493 | } else { |
| 494 | Carp::croak "BER_TYPE_REAL illegal decimal numerical representation format $format"; |
494 | Carp::croak "BER_TYPE_REAL invalid decimal numerical representation format $format"; |
| 495 | } |
495 | } |
| 496 | |
496 | |
| 497 | $val |
497 | $val |
| 498 | } |
498 | } |
| 499 | |
499 | |
| … | |
… | |
| 729 | dot, e.g. C<1.3.6.1.213>. |
729 | dot, e.g. C<1.3.6.1.213>. |
| 730 | |
730 | |
| 731 | =item C<BER_TYPE_RELOID> |
731 | =item C<BER_TYPE_RELOID> |
| 732 | |
732 | |
| 733 | Same as C<BER_TYPE_OID> but uses relative object identifier |
733 | Same as C<BER_TYPE_OID> but uses relative object identifier |
| 734 | encoding: ASN.1 has this hack of encoding the first two OID components |
734 | encoding: ASN.1 uses some hack encoding of the first two OID components |
| 735 | into a single integer in a weird attempt to save an insignificant amount |
735 | into a single integer in a weird attempt to save an insignificant amount |
| 736 | of space in an otherwise wasteful encoding, and relative OIDs are |
736 | of space in an otherwise wasteful encoding, and relative OIDs are |
| 737 | basically OIDs without this hack. The practical difference is that the |
737 | basically OIDs without this hack. The practical difference is that the |
| 738 | second component of an OID can only have the values 1..40, while relative |
738 | second component of an OID can only have the values 1..40, while relative |
| 739 | OIDs do not have this restriction. |
739 | OIDs do not have this restriction. |
