Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
home:Ledest:erlang:19
erlang
3556-Apply-suggestions-from-code-review.patch
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File 3556-Apply-suggestions-from-code-review.patch of Package erlang
From 6305684daf25fddca8a8922f3359a1881983b12f Mon Sep 17 00:00:00 2001 From: Lukas Larsson <lukas@erlang.org> Date: Wed, 19 May 2021 08:14:33 +0200 Subject: [PATCH 6/6] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Björn Gustavsson <bgustavsson@gmail.com> --- erts/doc/src/erlang.xml | 4 ++-- lib/stdlib/doc/src/io.xml | 5 ++--- system/doc/reference_manual/processes.xml | 4 ++-- 3 files changed, 6 insertions(+), 7 deletions(-) diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml index 08499ccd22..df592d809a 100644 --- a/erts/doc/src/erlang.xml +++ b/erts/doc/src/erlang.xml @@ -4367,7 +4367,7 @@ receive_replies(ReqId, N, Acc) -> are delivered to the process. If there is no connection to <c><anno>Node</anno></c>, an attempt is made to create one. If this fails, a <c>nodedown</c> message is delivered.</p> - <p>The delivery of the <c>nodedown</c> signal is not ordered towards other + <p>The delivery of the <c>nodedown</c> signal is not ordered with respect to other link or monitor signals from the node that goes down. If you need a guarantee that all signals from the remote node has been delivered before the <c>nodedown</c> signal is sent, you should use @@ -6108,7 +6108,7 @@ receive_replies(ReqId, N, Acc) -> <c><anno>Item</anno></c>s were included in <c><anno>ItemList</anno></c>. Valid <c><anno>Item</anno></c>s can be included multiple times in <c><anno>ItemList</anno></c>.</p> - <p>Getting process information follows the signal ordering guarentees + <p>Getting process information follows the signal ordering guarantees described in the <seealso marker="system/reference_manual:processes#signals"> Processes Chapter</seealso> in the <i>Erlang Reference Manual</i>.</p> diff --git a/lib/stdlib/doc/src/io.xml b/lib/stdlib/doc/src/io.xml index 99871c280b..9bea52c36e 100644 --- a/lib/stdlib/doc/src/io.xml +++ b/lib/stdlib/doc/src/io.xml @@ -1234,9 +1234,9 @@ enter><input>bar.</input> <p><c>standard_io</c> is an alias for <seealso marker="erts:erlang#group_leader/0"><c> group_leader/0</c></seealso>, so in order to change where the default input/output - requests are sent you can change the group leader using + requests are sent you can change the group leader for the current process using <seealso marker="erts:erlang#group_leader/2"><c> - group_leader(self(), NewGroupLeader).</c></seealso></p> + group_leader(NewGroupLeader, self()).</c></seealso></p> <p>There is always a process registered under the name of <c>user</c>. This can be used for sending output to the user.</p> @@ -1272,4 +1272,3 @@ Error: error 11</pre> Module:format_error(ErrorDescriptor)</code> </section> </erlref> - diff --git a/system/doc/reference_manual/processes.xml b/system/doc/reference_manual/processes.xml index 74ff2ba6e0..0ff4f0e01d 100644 --- a/system/doc/reference_manual/processes.xml +++ b/system/doc/reference_manual/processes.xml @@ -379,7 +379,7 @@ spawn(Module, Name, Args) -> pid() or <seealso marker="erts:erlang#whereis/1"><c>whereis/1</c></seealso> BIFs. The request signal is sent to the - <seealso marker="#runtime-service">name service</seealso> which + <seealso marker="#runtime-service">name service</seealso>, which responds with the reply signal. </item> @@ -402,7 +402,7 @@ spawn(Module, Name, Args) -> pid() <p><marker id="runtime-service"/> The clock service, the name service, the timer service, and the spawn - service mentioned above are services provided by the runtime system. + service mentioned previously are services provided by the runtime system. Each of these services consists of multiple independently executing entities. Such a service can be viewed as a group of processes, and could actually be implemented like that. Since each service consists of -- 2.26.2
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor