The variable 'S' was used twice. If the test case failed
because there were unused functions in asn1_SUITE, there
would be an ugly badmatch exception instead of the intended
nice error message.

* maint-20:
  Updated OTP version
  Prepare release
  Accept non-binary options as socket-options
  Bump version
  Fix broken handling of default values in extensions for PER
  compiler: Fix live regs update on allocate in validator
  Take fail labels into account when determining liveness in block ops
  Check for overflow when appending binaries, and error out with system_limit

Default values have never worked in extension for PER.

Note that for default values in the root part of SEQUENCE,
giving a value equal to the DEFAULT value, will result in
the same encoding as if asn1_DEFAULT was given. However,
that behavior is not promised by the documentation. The
documentation says that asn1_DEFAULT should be used for
default values. For DEFAULT in extensions, only implement
what the documentation promises and nothing more.

ERIERL-60

* maint-20:
  Updated OTP version
  Update release notes
  Update version numbers
  Fix doc for the 'quiet' option; it defaults to false
  asn1: Fix missing quotes of external encoding call
  Add a dedicated close function for TCP ports to prevent issues like ERL-430/448
  Close TCP ports properly on send timeout
  erts: Add missing release note

introduced by 8e4a9864385242b962ce7446f7daa4f58cfecca5.

EnumTypeName contains a hypen like fore example Cause-Misc. This caused
syntax errors when compiling the generated Erlang code.

Tags number above 16383 were not decoded correctly in
ber_decode_tag().

We could fix the problem, but there does not seem to be any need.

First, the only way that high tag numbers can be created is with
manual tagging; after 1994 manual tagging is no longer recommended.

Second, the ASN.1 playground (http://asn1-playground.oss.com) only
supports tags up to 16383 (the same is presumably true for OSS
Nokalva's other tools).

Therefore, clean up the existing code and make it an explicit
'invalid_tag' error when tags above 13383 are encountered
(instead of an implicit 'wrong_tag' error).