Erlang/OTP 24 Highlights - Erlang/OTP
Finally Erlang/OTP 24 is here! A release that for me has been about 10 years in the making. As is tradition by now, this blog post will go through the additions to Erlang/OTP that I am most excited about! Erlang/OTP 24 includes contributions from 60+ external contributors totalling 1400+ commits, 300+ PRs and changing 0.5 million(!) lines of code. Though I’m not sure the line number should count a
A few notes on message passing - Erlang/OTP
Message passing has always been central to Erlang, and while reasonably well-documented we’ve avoided going into too much detail to give us more freedom when implementing it. There’s nothing preventing us from describing it in a blog post though, so let’s have a closer look! Erlang processes communicate with each other by sending each other signals (not to be confused with Unix signals). There are
NIFs — Erlang System Documentation v27.0.1
View Source NIFs This section outlines an example of how to solve the example problem in Problem Example by using Native Implemented Functions (NIFs). NIFs are a simpler and more efficient way of calling C-code than using port drivers. NIFs are most suitable for synchronous functions, such as foo and bar in the example, that do some relatively short calculations without side effects and return the
A first look at the JIT - Erlang/OTP
Now that we’ve had a look at BEAM and the interpreter we’re going to explore one of the most exciting additions in OTP 24: the just-in-time compiler, or “JIT” for short. If you’re like me the word “JIT” probably makes you think of Hotspot (Java) or V8 (Javascript). These are very impressive pieces of engineering but they seem to have hijacked the term; not all JITs are that sophisticated, nor do t
A brief introduction to BEAM - Erlang/OTP
This post is a brief primer on BEAM, the virtual machine that executes user code in the Erlang Runtime System (ERTS). It’s intended to help those new to BEAM follow an upcoming series of posts about the JIT in OTP 24, leaving implementation details for later. BEAM is often confused with ERTS and it’s important to distinguish between the two; BEAM is just the virtual machine and it has no notion of
OTP 22 Highlights - Erlang/OTP
OTP 22 has just been released. It has been a long process with three release candidates before the final release. We decided this year to try to get one month more testing of the major release and I think that the extra time has paid off. We’ve received many bug reports from the community about large and small bugs that our internal tests did not find. This blog post will describe some highlights
proc_lib — stdlib v6.0.1
View Source proc_lib (stdlib v6.0.1) Functions for asynchronous and synchronous start of processes adhering to the OTP design principles. This module is used to start processes adhering to the OTP Design Principles. Specifically, the functions in this module are used by the OTP standard behaviors (for example, gen_server and gen_statem) when starting new processes. The functions can also be used t
Erlang OTP 21.0 is released | Erlang Programming Language
OTP 21 # Erlang/OTP 21 is a new major release with new features, improvements as well as incompatibilities. Potential Incompatibilities # All Corba applications are now moved from the OTP repository A new Corba repository will be created https://github.com/erlang New applications ftp and tftp, moved from inets ssl no longer supports 3_DES cipher suites or RSA-key exchange cipher suites by default
Interpreter optimization - Erlang/OTP
The BEAM interpreter in erts has been completely re-written in OTP 21. Most of the instructions have remained the same, but the perl scripts used to generate the C code have a new implementation. This blog post will look at some of the optimizations that were possible because of those changes. First however, let’s start with some basics about how the interpreter is built. The BEAM interpreter is b
Erlang -- inet
This module provides access to TCP/IP protocols. See also ERTS User's Guide: Inet Configuration for more information about how to configure an Erlang runtime system for IP communication. The following two Kernel configuration parameters affect the behavior of all sockets opened on an Erlang node: inet_default_connect_options can contain a list of default options used for all sockets returned when
gen_tcp — kernel v10.0.1
View Source gen_tcp (kernel v10.0.1) Interface to TCP/IP sockets. This module provides functions for communicating over TCP/IP protocol sockets. The following code fragment is a simple example of a client connecting to a server at port 5678, transferring a binary, and closing the connection: client() -> SomeHostInNet = "localhost", % to make it runnable on one machine {ok, Sock} = gen_tcp:connect(
application — kernel v10.0.1
View Source application behaviour (kernel v10.0.1) Generic OTP application functions In OTP, application denotes a component implementing some specific functionality, that can be started and stopped as a unit, and that can be reused in other systems. This module interacts with application controller, a process started at every Erlang runtime system. This module contains functions for controlling a
Applications — Erlang System Documentation v27.0.1
View Source Applications It is recommended to read this section alongside app and application in Kernel. Application Concept After creating code to implement a specific functionality, you might consider transforming it into an application — a component that can be started and stopped as a unit, as well as reused in other systems. The steps to create an application is as follows: Create an applicat
ets — stdlib v6.0.1
View Source ets (stdlib v6.0.1) Built-in term storage. This module is an interface to the Erlang built-in term storage BIFs. These provide the ability to store very large quantities of data in an Erlang runtime system, and to have constant access time to the data. (In the case of ordered_set, see below, access time is proportional to the logarithm of the number of stored objects.) Data is organize
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Further adventures in the JIT - Erlang/OTP
A closer look at the interpreter - Erlang/OTP
OTP 23 Highlights - Erlang/OTP
OTP 23 Release - Erlang/OTP
Erlang OTP 22.0 is released - Erlang/OTP
escript — stdlib v6.0.1