Asn1 Release Notes
Asn1 1.4.2
Fixed errors and malfunctions
-
When a component in a SEQUENCE is a CHOICE (or reference to a CHOICE)
and the SEQUENCE's component and one of the alternatives in the CHOICE
have identical names, an error may occur if one doesn't use the
'optimized' versions of the compiler. In the older versions (
ber,
ber_bin, per, per_bin
) one could optionally apply a value of a
component as {ComponentName,Value}
, and the generated code
chooses the second element of the tuple. However, a value of a CHOICE
must be applied as a tuple: {AlternativeName,Value}
. Thus,
in the rare case described above and if the value to the SEQUENCE's
component is not in a tuple notation the
{AlternativeName,Value}
will be peeled off in the SEQUENCE
and the value fed to the CHOICE will only be the Value
part of {AlternativeName,Value}
, and the encoder crashes.
The best way to avoid this is to use the optimized version of the
compiler where the unnecessary tuple notation
{ComponentName,Value}
no longer is allowed. Since it isn't
possible to solve this bug in the compiler.
(Own Id: OTP-4693)
Improvements and new features
-
Exclusive decode is enabled by a compiler option and a configuration
file. It makes it possible to leave parts of an ASN.1 encoded message
undecoded.
(Own Id: OTP-4744)
Asn1 1.4.1.1
Fixed errors and malfunctions
-
The documentation about how extensibility is handled is now corrected.
(Own Id: OTP-4663)
-
Function in object now calls the exported function
(Own Id: OTP-4665)
-
Now is tags for ObjectClassFieldType analyzed correctly.
(Own Id: OTP-4666)
Asn1 1.4.1
Fixed errors and malfunctions
-
Now is the Default value for an ENUMERATED returned as the name from
the NamedList when decoding.
(Own Id: OTP-4633)
-
It was an internal failure when permitted alphabet constraint existed
together with for instance a size constraint. E.g. when a
referenced type is constrained by a size constraint and the defined
type in turn is constrained by a permitted alphabet constraint.
(Own Id: OTP-4559)
-
Record is generated in hrl file for a CHOICE with extension mark
that has an internal SEQUENCE/SET definition.
(Own Id: OTP-4560)
-
Now is the length of a SEQUENCE/SET OF correctly encoded/decoded (PER).
(Own Id: OTP-4590)
-
The problem with unordered decoded terms when a component is a
ObjectClassFieldType has been solved.
(Own Id: OTP-4591)
Improvements and new features
-
More complex definitions with TableConstraints where the SimpleTable
and ComponentRelation are on different levels is now fully
supported. (Own Id: OTP-4631)
Asn1 1.4
Fixed errors and malfunctions
Improvements and new features
-
Each generated .erl file have now a function info/0 that returns
information about the used compiler version and options.
(Own Id: OTP-4373)
-
When compiling an ASN.1 module the compiler generates an Erlang module
that is compiled by the Erlang compiler. Earlier it was not possible to
add options to the final step, the Erlang compilation. By adding any
option that is not recognized as a specific ASN.1 option it will be
passed to the final step like:
erlc +debug_info
Mymodule.asn
or
asn1ct:compile('Mymodule',[debug_info])
.
(Own Id: OTP-4491)
-
Earlier one couldn't multi file compile modules that had different
tagdefaul, which now is possible. Equal Type/Value names in different
modules are resolved by renaming (concatenate type name and module
name): If two types with the same name T exist in module A and module B
they will get the new names TA and TB.
(Own Id: OTP-4492)
(Aux Id: OTP-3983)
-
BER: Encode/decode of data have been significantly improved. By use of
the compiler options
ber_bin
and optimize
,
optimized code will be generated and the optimized run-time module will
be used.
(Own Id: OTP-4493)
There are also release notes for
older versions.