The YouTube channel BEAM There, Done That has new video about the origin of the BEAM:
30 Years Inside the BEAM: Björn Gustavsson on Building Erlang’s Runtime
]]>The YouTube channel BEAM There, Done That has new video about native records and more:
Inside the BEAM: Björn Gustavsson on Maps, Records, and Runtime Design.
]]>Erlang/OTP 29 is a new major release with new features, improvements as well as a few incompatibilities. Some of the new features are highlighted below.
Many thanks to all contributors!
Added support for -unsafe attributes for marking
functions as unsafe to use. The compiler will by default now
generate warnings for calls to functions in Erlang/OTP known to be
always unsafe. Furthermore, xref can now be used to find calls to
unsafe functions and functions that lack documentation.
The SSH daemon now defaults to disabled for shell and exec services, implementing the “secure by default” principle. This prevents authenticated users from executing arbitrary Erlang code unless explicitly configured.
The SFTP subsystem is no longer enabled by default when starting an SSH daemon.
In SSL, the post quantum hybrid algorithm x25519mlkem768 is now the most preferred key exchange group in the default configuration.
The module io_ansi allows the user to emit Virtual Terminal
Sequences (also known as ANSI sequences) to the terminal in order to
add colors/styling to text or to create fully fledged terminal
applications.
The new ct_doctest module allows the user to test
documentation examples in Erlang module docs and documentation files.
The ignore_xref attribute has been handled as a post-analysis
filter by build tools such as Rebar3. In this release, [xref]
itself does the filtering, ensuring that all tooling that calls
xref for any purpose can rely on these declarations to just work.
In the default code path for the Erlang system, the current working
directory (.) is now in the last position instead of the first.
There is no longer a 32-bit Erlang/OTP build for Windows.
Native records as described in EEP-79 has been implemented. A native record is a data structure similar to the traditional tuple-based records, except that is a true data type. Native records are considered experimental in Erlang/OTP 29 and possibly also in Erlang/OTP 30.
The new is_integer/3 guard BIF makes it possible to easily verify
that a value is both an integer and within a certain range. For
example: is_integer(I, 0, 100)
Multi-valued comprehensions according to EEP 78
are now supported. For example, [-I, I || I <- [1, 2, 3]] will produce
[-1,1,-2,2,-3,3].
By enabling the compr_assign feature, it is now possible to bind variables
in a comprehensions. For example:
[H || E <- List, H = erlang:phash2(E), H rem 10 =:= 0]
In the documentation for the [compile] module, there is now a section
with recommendations for implementors of languages running on
the BEAM.
The JIT now generates better code for matching or creating binaries with multiple little-endian segments.
The compiler will generate more efficient code for map
comprehensions with constant values that don’t depend on the
generator. Example: #{K => 42 || K <- List}
There are several new compiler warnings enabled by default. For each such warning, there is an option to disable it.
There will now be a warning when using the catch operator, which
has been deprecated for a long time. It is recommended to instead
use try…catch but is also possible to disable the warning
by using the nowarn_deprecated_catch option.
There will now be a warning when exporting variables out of a
subexpression. For example: file:open(File, AllOpts = [write,
{encoding,utf8}]). This warning can be disabled using the
nowarn_export_var_subexpr compiler option.
The compiler will now warn for uses of the and and or
operators. This warning can be disabled using the
nowarn_obsolete_bool_op compiler option.
The compiler will now warn for matches such as {a,B} = {X,Y},
which is better written as {a=X,B=Y}. This warning can be disabled
using the nowarn_match_alias_pats option.
For a long time, there has been a warning for using the obsolete guard
tests (such as list(L) instead of is_list(L). In Erlang/OTP 30, the
old guards will be removed from the language.
rand:shuffle/1 and
rand:shuffle_s/2.For a full list and more details about new features and potential incompatibilities see the README.
]]>Erlang/OTP 28.5 is the fourth maintenance patch package for OTP 28, with mostly bug fixes as well as a few improvements.
There is a new “Secure Coding Guidelines” document in Design Principles describing how to write secure Erlang code.
A new configure option --{enable,disable}-use-embedded-3pp-alternatives has been added. When enabled, configure is forced to find alternatives,
to a subset, of the embedded third-party products (3pps) in the runtime system, and when disabled, configure will use all internal embedded 3pps.
Currently this option affects zstd, zlib, ryu (with STL), openssl and tcl. The default is to use all built-in embedded 3pps except for zlib
which by default will use zlib on the OS if available.
Requirements for alternatives:
zstd - Static library and include files of at least version 1.5.6 needs to be available.zlib - Library and include files of at least version 1.2.5 needs to be available.ryu (with STL) - A usable C++ compiler with C++17 support.openssl - No requirements. Our own MD5 implementation will be used.tcl - The strerrorname_np() function (introduced in glibc 2.32) mapping errno integers to symbolic names needs to be available.The argument embedded_3pps has been added to erlang:system_info/1. It returns a map with information about the use of embedded 3pps in the runtime
system.
For details about bugfixes and potential incompatibilities see the Erlang 28.5 README
The Erlang/OTP source can also be found at GitHub on the official Erlang repository, https://github.com/erlang/otp
Download links for this and previous versions are found here:
]]>Erlang/OTP 29.0-rc3 is the third and final release candidate before the OTP 29.0 release.
The intention with this release is to get feedback from our users. All feedback is welcome, even if it is only to say that it works for you. We encourage users to try it out and give us feedback either by creating an issue at https://github.com/erlang/otp/issues or by posting to Erlang Forums.
All artifacts for the release can be downloaded from the Erlang/OTP Github release and you can view the new documentation at https://erlang.org/documentation/doc-17.0-rc3/doc. You can also install the latest release using kerl like this:
kerl build 29.0-rc3 29.0-rc3.
Erlang/OTP 29 is a new major release with new features, improvements as well as a few incompatibilities. Some of the new features are highlighted below.
Many thanks to all contributors!
Added support for -unsafe attributes for marking
functions as unsafe to use. The compiler will by default now
generate warnings for calls to functions in Erlang/OTP known to be
always unsafe. Furthermore, xref can now be used to find calls to
unsafe functions and functions that lack documentation.
The SSH daemon now defaults to disabled for shell and exec services, implementing the “secure by default” principle. This prevents authenticated users from executing arbitrary Erlang code unless explicitly configured.
The SFTP subsystem is no longer enabled by default when starting an SSH daemon.
In SSL, the post quantum hybrid algorithm x25519mlkem768 is now the most preferred key exchange group in the default configuration.
The module io_ansi allows the user to emit Virtual Terminal
Sequences (also known as ANSI sequences) to the terminal in order to
add colors/styling to text or to create fully fledged terminal
applications.
The new ct_doctest module allows the user to test
documentation examples in Erlang module docs and documentation files.
The ignore_xref attribute has been handled as a post-analysis
filter by build tools such as Rebar3. In this release, [xref]
itself does the filtering, ensuring that all tooling that calls
xref for any purpose can rely on these declarations to just work.
In the default code path for the Erlang system, the current working
directory (.) is now in the last position instead of the first.
There is no longer a 32-bit Erlang/OTP build for Windows.
Native records as described in EEP-79 has been implemented. A native record is a data structure similar to the traditional tuple-based records, except that is a true data type. Native records are considered experimental in Erlang/OTP 29 and possibly also in Erlang/OTP 30.
The new is_integer/3 guard BIF makes it possible to easily verify
that a value is both an integer and within a certain range. For
example: is_integer(I, 0, 100)
Multi-valued comprehensions according to EEP 78
are now supported. For example, [-I, I || I <- [1, 2, 3]] will produce
[-1,1,-2,2,-3,3].
By enabling the compr_assign feature, it is now possible to bind variables
in a comprehensions. For example:
[H || E <- List, H = erlang:phash2(E), H rem 10 =:= 0]
In the documentation for the [compile] module, there is now a section
with recommendations for implementors of languages running on
the BEAM.
The JIT now generates better code for matching or creating binaries with multiple little-endian segments.
The compiler will generate more efficient code for map
comprehensions with constant values that don’t depend on the
generator. Example: #{K => 42 || K <- List}
There are several new compiler warnings enabled by default. For each such warning, there is an option to disable it.
There will now be a warning when using the catch operator, which
has been deprecated for a long time. It is recommended to instead
use try…catch but is also possible to disable the warning
by using the nowarn_deprecated_catch option.
There will now be a warning when exporting variables out of a
subexpression. For example: file:open(File, AllOpts = [write,
{encoding,utf8}]). This warning can be disabled using the
nowarn_export_var_subexpr compiler option.
The compiler will now warn for uses of the and and or
operators. This warning can be disabled using the
nowarn_obsolete_bool_op compiler option.
The compiler will now warn for matches such as {a,B} = {X,Y},
which is better written as {a=X,B=Y}. This warning can be disabled
using the nowarn_match_alias_pats option.
For a long time, there has been a warning for using the obsolete guard
tests (such as list(L) instead of is_list(L). In Erlang/OTP 30, the
old guards will be removed from the language.
rand:shuffle/1 and
rand:shuffle_s/2.For more details about new features and potential incompatibilities see the README.
]]>Erlang/OTP 29.0-rc2 is the second release candidate of three before the OTP 29.0 release.
The intention with this release is to get feedback from our users. All feedback is welcome, even if it is only to say that it works for you. We encourage users to try it out and give us feedback either by creating an issue at https://github.com/erlang/otp/issues or by posting to Erlang Forums.
All artifacts for the release can be downloaded from the Erlang/OTP Github release and you can view the new documentation at https://erlang.org/documentation/doc-17.0-rc2/doc. You can also install the latest release using kerl like this:
kerl build 29.0-rc2 29.0-rc2.
Erlang/OTP 29 is a new major release with new features, improvements as well as a few incompatibilities. Some of the new features are highlighted below.
Many thanks to all contributors!
The module io_ansi allows the user to emit Virtual Terminal
Sequences (also known as ANSI sequences) to the terminal in order to
add colors/styling to text or to create fully fledged terminal
applications.
The new ct_doctest module allows the user to test
documentation examples in Erlang module docs and documentation files.
The ignore_xref attribute has been handled as a post-analysis
filter by build tools such as Rebar3. In this release, [xref]
itself does the filtering, ensuring that all tooling that calls
xref for any purpose can rely on these declarations to just work.
In the default code path for the Erlang system, the current working
directory (.) is now in the last position instead of the first.
There is no longer a 32-bit Erlang/OTP build for Windows.
Native records as described in EEP-79 has been implemented. A native record is a data structure similar to the traditional tuple-based records, except that is a true data type. Native records are considered experimental in Erlang/OTP 29 and possibly also in Erlang/OTP 30.
The new is_integer/3 guard BIF makes it possible to easily verify
that a value is both an integer and within a certain range. For
example: is_integer(I, 0, 100)
Multi-valued comprehensions according to EEP 78
are now supported. For example, [-I, I || I <- [1, 2, 3]] will produce
[-1,1,-2,2,-3,3].
By enabling the compr_assign feature, it is now possible to bind variables
in a comprehensions. For example:
[H || E <- List, H = erlang:phash2(E), H rem 10 =:= 0]
In the documentation for the [compile] module, there is now a section
with recommendations for implementors of languages running on
the BEAM.
The JIT now generates better code for matching or creating binaries with multiple little-endian segments.
The compiler will generate more efficient code for map
comprehensions with constant values that don’t depend on the
generator. Example: #{K => 42 || K <- List}
There are several new compiler warnings enabled by default. For each such warning, there is an option to disable it.
There will now be a warning when using the catch operator, which
has been deprecated for a long time. It is recommended to instead
use try…catch but is also possible to disable the warning
by using the nowarn_deprecated_catch option.
There will now be a warning when exporting variables out of a
subexpression. For example: file:open(File, AllOpts = [write,
{encoding,utf8}]). This warning can be disabled using the
nowarn_export_var_subexpr compiler option.
The compiler will now warn for uses of the and and or
operators. This warning can be disabled using the
nowarn_obsolete_bool_op compiler option.
The compiler will now warn for matches such as {a,B} = {X,Y},
which is better written as {a=X,B=Y}. This warning can be disabled
using the nowarn_match_alias_pats option.
For a long time, there has been a warning for using the obsolete guard
tests (such as list(L) instead of is_list(L). In Erlang/OTP 30, the
old guards will be removed from the language.
rand:shuffle/1 and
rand:shuffle_s/2.For more details about new features and potential incompatibilities see the README.
]]>Erlang/OTP 28.4 is the third maintenance patch package for OTP 28, with mostly bug fixes as well as improvements.
badarg exception if the
term exists with a different value.{autoretry, timeout()} to httpc:request/4,5. This
option allows the client to decide how to act upon receiving a Retry-After
response header. The default behavior changes, as now only one retry is made
before returning the error code, instead of retrying infinitely.For details about bugfixes and potential incompatibilities see the Erlang 28.4 README
The Erlang/OTP source can also be found at GitHub on the official Erlang repository, https://github.com/erlang/otp
Download links for this and previous versions are found here:
]]>Erlang/OTP 29.0-rc1 is the first release candidate of three before the OTP 29.0 release.
The intention with this release is to get feedback from our users. All feedback is welcome, even if it is only to say that it works for you. We encourage users to try it out and give us feedback either by creating an issue at https://github.com/erlang/otp/issues or by posting to Erlang Forums.
All artifacts for the release can be downloaded from the Erlang/OTP Github release and you can view the new documentation at https://erlang.org/documentation/doc-17.0-rc1/doc. You can also install the latest release using kerl like this:
kerl build 29.0-rc1 29.0-rc1.
Erlang/OTP 29 is a new major release with new features, improvements as well as a few incompatibilities. Some of the new features are highlighted below.
Many thanks to all contributors!
In the default code path for the Erlang system, the current working
directory (.) is now in the last position instead of the first.
There is no longer a 32-bit Erlang/OTP build for Windows.
Native records as described in EEP-79 has been implemented. A native record is a data structure similar to the traditional tuple-based records, except that is a true data type. Native records are considered experimental in Erlang/OTP 29 and possibly also in Erlang/OTP 30.
The new is_integer/3 guard BIF makes it possible to easily verify
that a value is both an integer and within a certain range. For
example: is_integer(I, 0, 100)
Multi-valued comprehensions according to EEP 78
are now supported. For example, [-I, I || I <- [1, 2, 3]] will produce
[-1,1,-2,2,-3,3].
By enabling the compr_assign feature, it is now possible to bind variables
in a comprehensions. For example:
[H || E <- List, H = erlang:phash2(E), H rem 10 =:= 0]
In the documentation for the [compile] module, there is now a section
with recommendations for implementors of languages running on
the BEAM.
The JIT now generates better code for matching or creating binaries with multiple little-endian segments.
The compiler will generate more efficient code for map
comprehensions with constant values that don’t depend on the
generator. Example: #{K => 42 || K <- List}
There are several new compiler warnings enabled by default. For each such warning, there is an option to disable it.
There will now be a warning when using the catch operator, which
has been deprecated for a long time. It is recommended to instead
use try…catch but is also possible to disable the warning
by using the nowarn_deprecated_catch option.
There will now be a warning when exporting variables out of a
subexpression. For example: file:open(File, AllOpts = [write,
{encoding,utf8}]). This warning can be disabled using the
nowarn_export_var_subexpr compiler option.
The compiler will now warn for uses of the and and or
operators. This warning can be disabled using the
nowarn_obsolete_bool_op compiler option.
The compiler will now warn for matches such as {a,B} = {X,Y},
which is better written as {a=X,B=Y}. This warning can be disabled
using the nowarn_match_alias_pats option.
For a long time, there has been a warning for using the obsolete guard
tests (such as list(L) instead of is_list(L). In Erlang/OTP 30, the
old guards will be removed from the language.
rand:shuffle/1 and
rand:shuffle_s/2.For more details about new features and potential incompatibilities see the README.
]]>Erlang/OTP 28.3 is the second maintenance patch package for OTP 28, with mostly bug fixes as well as improvements.
gen_tcp, as well as TCP_USER_TIMEOUT for both
gen_tcp and socket.Publish OpenVEX statements in https://erlang.org/download/vex/
OpenVEX statements contain the same information as the OTP advisories, with
the addition of vendor CVEs for which Erlang/OTP is not affected. This is
important to silence vulnerability scanners that may claim Erlang/OTP to be
vulnerable to vendor dependency projects, e.g., openssl.
OpenVEX statements will be published in https://erlang.org/download/vex/ where there will be an OTP file per release, e.g., https://erlang.org/download/vex/otp-28.openvex.json.
Erlang/OTP publishes OpenVEX statements for all supported releases, that is, as of today, OTP-26, OTP-27, and OTP-28.
The source SBOM tooling (oss-review-toolkit) has been updated to produce source SBOM in SPDX v2.3 format, and the source SBOM now links OpenVEX statements to a security external reference. This means that by simply analyzing the source SBOM, everyone can further read the location of the OpenVEX statements and further process them.
For details about bugfixes and potential incompatibilities see the Erlang 28.3 README
The Erlang/OTP source can also be found at GitHub on the official Erlang repository, https://github.com/erlang/otp
Download links for this and previous versions are found here:
]]>Erlang/OTP 28.1 is the first maintenance patch package for OTP 28, with mostly bug fixes as well as improvements.
inet_dns_tsig and inet_res modules have been fixed to TSIG
verify the correct timestamp.
In the process two undocumented error code atoms have been corrected to
notauth and notzone to adhere to the DNS RFCs. Code that relied on the
previous incorrect values may have to be corrected.dbg is now available in the documentation.For details about bugfixes and potential incompatibilities see the Erlang 28.1 README
The Erlang/OTP source can also be found at GitHub on the official Erlang repository, https://github.com/erlang/otp
Download links for this and previous versions are found here:
]]>