| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Communication between Erlang processes has conceptually always been
performed through asynchronous signaling. The runtime system
implementation has however previously preformed most operation
synchronously. In a system with only one true thread of execution, this
is not problematic (often the opposite). In a system with multiple threads
of execution (as current runtime system implementation with SMP support)
it becomes problematic. This since it often involves locking of structures
when updating them which in turn cause resource contention. Utilizing
true asynchronous communication often avoids these resource contention
issues.
The case that triggered this change was contention on the link lock due
to frequent updates of the monitor trees during communication with a
frequently used server. The signal order delivery guarantees of the
language makes it hard to change the implementation of only some signals
to use true asynchronous signaling. Therefore the implementations
of (almost) all signals have been changed.
Currently the following signals have been implemented as true
asynchronous signals:
- Message signals
- Exit signals
- Monitor signals
- Demonitor signals
- Monitor triggered signals (DOWN, CHANGE, etc)
- Link signals
- Unlink signals
- Group leader signals
All of the above already defined as asynchronous signals in the
language. The implementation of messages signals was quite
asynchronous to begin with, but had quite strict delivery constraints
due to the ordering guarantees of signals between a pair of processes.
The previously used message queue partitioned into two halves has been
replaced by a more general signal queue partitioned into three parts
that service all kinds of signals. More details regarding the signal
queue can be found in comments in the erl_proc_sig_queue.h file.
The monitor and link implementations have also been completely replaced
in order to fit the new asynchronous signaling implementation as good
as possible. More details regarding the new monitor and link
implementations can be found in the erl_monitor_link.h file.
|
|
* maint:
Add updated type-spec to Emacs skeletons of OTP behaviours
|
|
* pr/1620:
Add updated type-spec to Emacs skeletons of OTP behaviours
|
|
The changes are based on the latest versions of following modules
and are also similar to gen_statem Emacs skeleton. Note that the
gen_fsm is not updated because it is deprecated.
application:
* add/update type-spec for all callbacks
* add start_phase/3 callback
* add prep_stop/1 callback
* add config_change/3 callback
supervisor:
* add/update type-spec for all callbacks
supervisor_bridge:
* add/update type-spec for all callbacks
gen_server:
* add/update type-spec for all callbacks
* add format_status/2 callback
gen_event:
* add/update type-spec for all callbacks
* add format_status/2 callback
|
|
* maint:
Derive `erlang-shell-mode` properly from `comint-mode`
|
|
|
|
* maint:
emacs: delimiter first in icr works
emacs: Indent delimiter first in term elements correctly
emacs: Indent tuple (and maps) elements as list elements
Add emacs indention testcase
|
|
|
|
|
|
Avoid
From:
{
^^element1,
^^element2
}
To:
{
^element1,
^element2
}
|
|
Split the manual testcase and run them in daily tests instead.
Easy to run directly as well:
(cd ../test; cerl -eval "emacs_SUITE:indent([])")
|
|
|
|
|
|
|
|
|
|
|
|
* maint:
Update the version to 2.8.0
Remove the obsolete erlang-buffer-substring function
Add a :package-version property to the new defcustom erlang-shell-prompt-read-only
Bump the version number
Make the erlang-shell prompt read-only by default
Remove a mention of Emacs 21
Drop some redundant backwards compatibility code
Enable lexical binding for erlang-mode
Remove some ancient compatibility aliases
|
|
* upstream/pr/1474:
Update the version to 2.8.0
Remove the obsolete erlang-buffer-substring function
Add a :package-version property to the new defcustom erlang-shell-prompt-read-only
Bump the version number
Make the erlang-shell prompt read-only by default
Remove a mention of Emacs 21
Drop some redundant backwards compatibility code
Enable lexical binding for erlang-mode
Remove some ancient compatibility aliases
|
|
|
|
* maint:
Emacs: Update erlang-xref-find-definitions-module for Emacs 26
Emacs: Guess type of tag definition in Emacs 24
|
|
|
|
|
|
OTP-14520
|
|
The number of arguments to visit-tags-table-buffer have
increased in Emacs 26.
|
|
This concerns tag finding commands in Emacs 24. If the word at point
is preceded by a hash suggest as default a jump to a record
definition. If it is a question mark suggest a macro. Otherwise
assume it is a function. If it is not a qualified call assume it is a
local function.
|
|
OTP-14520
|
|
Conflicts:
erts/emulator/beam/bif.c
erts/emulator/beam/dist.c
erts/emulator/beam/dist.h
erts/emulator/beam/erl_bif_info.c
erts/emulator/beam/erl_node_tables.c
erts/emulator/beam/erl_node_tables.h
erts/emulator/beam/external.c
|
|
|
|
The default target is changed to be just the name at point when
xref-find-references is invoked. Previously the default was the same
as for xref-find-definitions. This included arity and other things
that do not make sense for xref-find-references.
|
|
|
|
|
|
|
|
erlang-shell-prompt-read-only
|
|
|
|
Allow for this behaviour to be customized via a defcustom.
|
|
|
|
|
|
|
|
|
|
Those were added 8 years ago and it's about time they were removed.
Now that we depend on a newer Emacs release, we can also drop the
function `erlang-obsolete`.
|
|
* dgud/emacs/update-bifs:
Update available bifs for 20
|
|
|
|
Fix loading of byte-compiled erlang.elc on Emacs 25
and the erlang shell.
|
|
Drop some legacy Emacs compatibility code
|
|
|
|
Follow the same pattern as pid_to_list
|
|
|
|
All of those are present on the target Emacs 24.1.
|
|
|
