diff options
Diffstat (limited to 'lib/asn1/doc')
-rw-r--r-- | lib/asn1/doc/src/asn1ct.xml | 9 | ||||
-rw-r--r-- | lib/asn1/doc/src/notes.xml | 60 |
2 files changed, 68 insertions, 1 deletions
diff --git a/lib/asn1/doc/src/asn1ct.xml b/lib/asn1/doc/src/asn1ct.xml index 23d122f69a..fcd77e9dc6 100644 --- a/lib/asn1/doc/src/asn1ct.xml +++ b/lib/asn1/doc/src/asn1ct.xml @@ -66,7 +66,7 @@ <v>Option = ber | per | uper | der | compact_bit_string | legacy_bit_string | noobj | {n2n, EnumTypeName} |{outdir, Dir} | {i, IncludeDir} | - asn1config | undec_rest | + asn1config | undec_rest | no_ok_wrapper | {macro_name_prefix, Prefix} | {record_name_prefix, Prefix} | verbose | warnings_as_errors</v> <v>OldOption = ber | per</v> <v>Reason = term()</v> @@ -238,6 +238,13 @@ File3.asn </pre> list or a binary. Earlier versions of the compiler ignored those following bytes.</p> </item> + <tag><c>no_ok_wrapper</c></tag> + <item> + <p>If this option is given, the generated <c>encode/2</c> + and <c>decode/2</c> functions will not wrap a successful + return value in an <c>{ok,...}</c> tuple. If any error + occurs, there will be an exception.</p> + </item> <tag><c>{macro_name_prefix, Prefix}</c></tag> <item> <p>All macro names generated by the compiler are prefixed with diff --git a/lib/asn1/doc/src/notes.xml b/lib/asn1/doc/src/notes.xml index e4d9edd709..a00fc3de36 100644 --- a/lib/asn1/doc/src/notes.xml +++ b/lib/asn1/doc/src/notes.xml @@ -31,6 +31,66 @@ <p>This document describes the changes made to the asn1 application.</p> +<section><title>Asn1 2.0.4</title> + + <section><title>Fixed Bugs and Malfunctions</title> + <list> + <item> + <p> + The default value for a <c>BIT STRING</c> would not + always be recognized, causing the encoding to be + incorrect for the DER/PER/UPER encodings.</p> + <p> + Own Id: OTP-11319</p> + </item> + <item> + <p> + The <c>asn1</c> application would fail to build if the + <c>.erlang</c> file printed something to standard output.</p> + <p> + Own Id: OTP-11360</p> + </item> + <item> + <p>An union of integer ranges in an INTEGER constraint + could sometimes be interpreted as the intersection of the + range.</p> + <p> + Own Id: OTP-11411 Aux Id: seq12443 </p> + </item> + <item> + <p> + Extensible, multiple single value constraints (such as + <c>INTEGER (1|17, ...)</c>) would be incorrectly encoded.</p> + <p> + Own Id: OTP-11415</p> + </item> + <item> + <p> + The ASN.1 compiler would fail to compile a constraint + with values given for for the extension part (such as + <c>INTEGER (1..10, ..., 11..20)</c>).</p> + <p> + Own Id: OTP-11504</p> + </item> + </list> + </section> + + + <section><title>Improvements and New Features</title> + <list> + <item> + <p> + The new option '<c>no_ok_wrapper</c>' generates + M:encode/2 and M:decode/2 functions that don't wrap the + return value in an {ok,...} tuple.</p> + <p> + Own Id: OTP-11314</p> + </item> + </list> + </section> + +</section> + <section><title>Asn1 2.0.3</title> <section><title>Fixed Bugs and Malfunctions</title> |