www.pudn.com > cryptix-asn1-0.1.11.zip > KnownLimitations

* if OID definitions are not placed at the top of the specifications file, the
  generated values are incorrect.

  workaround: group OID definitions and place them before type assignments.

* elements of compound types should either be built-in ASN.1 types or user-
  defined types; ie. specifications of the form:

  A ::= SEQUENCE {
     a1  OBJECT IDENTIFIER,
     a2  SET OF B
  }

  shall not generate valid code.  use instead:

  A ::= SEQUENCE {
     a1  OBJECT IDENTIFIER,
     a2  BList
  }

  BList ::= SET OF B

  // include the INTEGER {v1(0)} cases...

  workaround: define additional types.

* CHOICE constructs are not always handled properly.

  workaround: none.

* DEFAULT values for compound types cause generation of Illegal Java code.

  workaround: none.  dont use them for the moment.

* ENUMERATED types are not supported yet.