2 0. ASN.1 grammar parser is written mostly with respect to constructing a tree,
3 so a tree destruction is not fully supported and certain memory leaks are
4 known. Not a huge problem for run-once programs like a compiler.
5 NOTE: This statement does not apply to the target code _produced_
8 1. For purposes of compilation, INTEGER type is modelled using a large
9 static type (asn_integer_t), but defined as any positive or negative value
10 by ASN.1. Not a problem as most specifications use very small values anyway.
11 NOTE: This statement does not apply to the target code _produced_
14 2. A MACRO facility is part of obsolete ASN.1 standard, and is not supported.
16 3. Multiple tags applied at the same level are not supported:
17 BadTags ::= [0] EXPLICIT [2] IMPLICIT OtherType
18 The same thing could be achieved by using the indirection:
19 GoodTags ::= [0] EXPLICIT OtherTypePtr
20 OtherTypePtr ::= [2] IMPLICIT OtherType
22 4. Mixed definite/indefinite length in a _single_ BER tags sequence is not
23 supported. Should not be a problem in the real world. Please note that it
24 is still possible, for example, to encode a wrapper structure using definite
25 length, and encode its substructure member using indefinite length. The BER
26 decoder is perfectly capable of decoding such sequences.
28 5. Encoding or decoding of structures with combined length greater than 16MB
31 6. XER codec does not support integer (INTEGER, ENUMERATED) values
32 outside the signed long range.