...
It is also possible to use sequential formats to describe constructed ASN.1 types. In this case the tag must be declared as constructed (a specific a specific keyword) to allow Ultra to correctly encode the type.
...
Since INTEGER types are automatically mapped to int, which is a 32-bit integer type, INTEGERs longer than 4 bytes will cause decoding errors. This can be avoided by using the bigint type in place of INTEGER. The only difference between bigint and INTEGER is that bigint is automatically mapped to the the
bigint type, which can support INTEGERs of any size.
...
For string types, constraints on the permitted alphabet are not handled.
Fragmented encoding (encoding for large size fields) is not supported.
Not all character types are supported. Currently only the
GraphicalString, IA5String, VisibleString, NumericString, andUTF8Stringare supported.
| Scroll pagebreak |
|---|