From ad6e765bcd4f35a282ef00e38ed9129f3a5c1d83 Mon Sep 17 00:00:00 2001 From: Hans Bolinder Date: Thu, 1 Sep 2016 14:32:27 +0200 Subject: doc: Correct errors introduced by Editorial changes Fix some older errors as well. --- lib/kernel/doc/src/app.xml | 6 +++--- lib/kernel/doc/src/application.xml | 6 +++--- lib/kernel/doc/src/auth.xml | 4 ++-- lib/kernel/doc/src/code.xml | 12 ++++++------ lib/kernel/doc/src/erl_boot_server.xml | 4 ++-- lib/kernel/doc/src/erl_ddll.xml | 6 +++--- lib/kernel/doc/src/error_logger.xml | 30 +++++++++++++++--------------- lib/kernel/doc/src/file.xml | 28 ++++++++++++++-------------- lib/kernel/doc/src/gen_tcp.xml | 6 +++--- lib/kernel/doc/src/inet.xml | 22 +++++++++++----------- lib/kernel/doc/src/init_stub.xml | 2 +- lib/kernel/doc/src/kernel_app.xml | 20 ++++++++++---------- lib/kernel/doc/src/net_kernel.xml | 12 ++++++------ lib/kernel/doc/src/notes.xml | 2 +- lib/kernel/doc/src/rpc.xml | 4 ++-- lib/kernel/doc/src/zlib_stub.xml | 2 +- 16 files changed, 83 insertions(+), 83 deletions(-) (limited to 'lib/kernel/doc') diff --git a/lib/kernel/doc/src/app.xml b/lib/kernel/doc/src/app.xml index 5e0da409a3..d2e9390d7e 100644 --- a/lib/kernel/doc/src/app.xml +++ b/lib/kernel/doc/src/app.xml @@ -151,7 +151,7 @@ ApplicationVersion = string() application is allowed to be started. systools uses this list to generate correct start scripts. Defaults to the empty list, but notice that all applications have - dependencies to (at least) Kernel and STDLIB.

+ dependencies to (at least) Kernel and STDLIB.

env @@ -171,7 +171,7 @@ ApplicationVersion = string() implemented as a supervision tree, otherwise the application controller does not know how to start it. mod can be omitted for applications without processes, typically - code libraries, for example, STDLIB.

+ code libraries, for example, STDLIB.

 start_phases @@ -236,7 +236,7 @@ ApplicationVersion = string()
See Also

application(3), - sasl:systools(3)

+ systools(3)

diff --git a/lib/kernel/doc/src/application.xml b/lib/kernel/doc/src/application.xml index 8d33aa86e7..886286b76d 100644 --- a/lib/kernel/doc/src/application.xml +++ b/lib/kernel/doc/src/application.xml @@ -200,7 +200,7 @@ app(4).

If Distributed == {Application,[Time,]Nodes}, the application becomes distributed. The argument overrides - the value for the application in the Kernel configuration + the value for the application in the Kernel configuration parameter distributed. Application must be the application name (same as in the first argument). If a node crashes and Time is specified, @@ -221,7 +221,7 @@ Nodes = [cp1@cave, {cp2@cave, cp3@cave}] the application is to be started at cp2@cave or cp3@cave.

If Distributed == default, the value for - the application in the Kernel configuration parameter + the application in the Kernel configuration parameter distributed is used.

@@ -267,7 +267,7 @@ Nodes = [cp1@cave, {cp2@cave, cp3@cave}] started, Application is started as well.

By default, all applications are loaded with permission true on all nodes. The permission can be configured - using the Kernel configuration parameter permissions.

+ using the Kernel configuration parameter permissions.

diff --git a/lib/kernel/doc/src/auth.xml b/lib/kernel/doc/src/auth.xml index 03f983b96d..5901446960 100644 --- a/lib/kernel/doc/src/auth.xml +++ b/lib/kernel/doc/src/auth.xml @@ -47,7 +47,7 @@

Use erlang:get_cookie() - in ERTS instead.

+ in ERTS instead.

 @@ -59,7 +59,7 @@

Use erlang:set_cookie(node(), Cookie) - in ERTS instead.

+ in ERTS instead.

 diff --git a/lib/kernel/doc/src/code.xml b/lib/kernel/doc/src/code.xml index 21f8a2d54a..4db377bcde 100644 --- a/lib/kernel/doc/src/code.xml +++ b/lib/kernel/doc/src/code.xml @@ -86,11 +86,11 @@ an ebin directory are ignored.

All application directories found in the additional directories appears before the standard OTP applications, except for the - Kernel and STDLIB applications, which are placed before + Kernel and STDLIB applications, which are placed before any additional applications. In other words, modules found in any of the additional library directories override modules with - the same name in OTP, except for modules in Kernel and - STDLIB.

+ the same name in OTP, except for modules in Kernel and + STDLIB.

Environment variable ERL_LIBS (if defined) is to contain a colon-separated (for Unix-like systems) or semicolon-separated (for Windows) list of additional libraries.

@@ -151,7 +151,7 @@ zip:create("mnesia-4.4.7.ez", $OTPROOT/lib/mnesia.ez/mnesia/ebin or $OTPROOT/lib/mnesia-4.4.7.ez/mnesia-4.4.7/ebin.

-

The code server uses module erl_prim_loader in ERTS +

The code server uses module erl_prim_loader in ERTS (possibly through erl_boot_server) to read code files from archives. However, the functions in erl_prim_loader can also be used by other applications to read files from archives. For @@ -688,9 +688,9 @@ ok = code:finish_loading(Prepared),

Normally, Loaded is the absolute filename Filename from which the code is obtained. If the module is preloaded (see - sasl:script(4)), + script(4)), Loaded==preloaded. If the module is Cover-compiled (see - tools:cover(3)), + cover(3)), Loaded==cover_compiled.

 diff --git a/lib/kernel/doc/src/erl_boot_server.xml b/lib/kernel/doc/src/erl_boot_server.xml index 897365f9b9..4109251387 100644 --- a/lib/kernel/doc/src/erl_boot_server.xml +++ b/lib/kernel/doc/src/erl_boot_server.xml @@ -38,13 +38,13 @@ command-line flag -loader inet. All hosts specified with command-line flag -hosts Host must have one instance of this server running.

-

This server can be started with the Kernel configuration +

This server can be started with the Kernel configuration parameter start_boot_server.

The erl_boot_server can read regular files and files in archives. See code(3) and erl_prim_loader(3) - in ERTS.

+ in ERTS.

The support for loading code from archive files is experimental. It is released before it is ready to obtain early feedback. The file format, semantics, diff --git a/lib/kernel/doc/src/erl_ddll.xml b/lib/kernel/doc/src/erl_ddll.xml index a5ce58ef3e..75114e015c 100644 --- a/lib/kernel/doc/src/erl_ddll.xml +++ b/lib/kernel/doc/src/erl_ddll.xml @@ -201,7 +201,7 @@

Removes a driver monitor in much the same way as erlang:demonitor/1 - in ERTS + in ERTS does with process monitors. For details about how to create driver monitors, see monitor/2, @@ -431,7 +431,7 @@

Creates a driver monitor and works in many ways as erlang:monitor/2 - in ERTS, + in ERTS, does for processes. When a driver changes state, the monitor results in a monitor message that is sent to the calling process. MonitorRef returned by this function is @@ -745,7 +745,7 @@

This parameter is the name of the driver to be used in subsequent calls to function erlang:open_port - in ERTS. + in ERTS. The name can be specified as an iolist() or an atom(). The name specified when loading is used to find the object file (with the help of Path diff --git a/lib/kernel/doc/src/error_logger.xml b/lib/kernel/doc/src/error_logger.xml index a8273e59e2..814e8eac46 100644 --- a/lib/kernel/doc/src/error_logger.xml +++ b/lib/kernel/doc/src/error_logger.xml @@ -33,7 +33,7 @@

The Erlang error logger is an event manager (see OTP Design Principles and - stdlib:gen_event(3)), + gen_event(3)), registered as error_logger. Errors, warnings, and info events are sent to the error logger from the Erlang runtime system and the different Erlang/OTP applications. The events are, by default, @@ -44,12 +44,12 @@ executing.

Initially, error_logger has only a primitive event handler, which buffers and prints the raw event messages. During - system startup, the Kernel application replaces this with a + system startup, the Kernel application replaces this with a standard event handler, by default one that writes - nicely formatted output to the terminal. Kernel can also be + nicely formatted output to the terminal. Kernel can also be configured so that events are logged to a file instead, or not logged at all, see kernel(6).

-

Also the SASL application, if started, adds its own event +

Also the SASL application, if started, adds its own event handler, which by default writes supervisor, crash, and progress reports to the terminal. See sasl(6).

@@ -58,9 +58,9 @@ User-defined event handlers can be added to handle application-specific events, see add_report_handler/1,2. - Also, a useful event handler is provided in STDLIB for multi-file + Also, a useful event handler is provided in STDLIB for multi-file logging of events, see - stdlib:log_mf_h(3).

+ log_mf_h(3).

Warning events were introduced in Erlang/OTP R9C and are enabled by default as from Erlang/OTP 18.0. To retain backwards compatibility with existing user-defined event handlers, the warning events can be @@ -82,7 +82,7 @@

Adds a new event handler to the error logger. The event handler must be implemented as a gen_event callback module, see - stdlib:gen_event(3).

+ gen_event(3).

Handler is typically the name of the callback module and Args is an optional term (defaults to []) passed to the initialization callback function Handler:init/1. @@ -97,7 +97,7 @@

Deletes an event handler from the error logger by calling gen_event:delete_handler(error_logger, Handler, []), - see stdlib:gen_event(3).

+ see gen_event(3).

@@ -110,7 +110,7 @@ The Format and Data arguments are the same as the arguments of io:format/2 - in STDLIB. + in STDLIB. The event is handled by the standard event handler.

Example:

@@ -171,7 +171,7 @@ ok
The Format and Data arguments are the same as the arguments of io:format/2 - in STDLIB. The event is handled by the standard event handler.

+ in STDLIB. The event is handled by the standard event handler.

Example:

 1> error_logger:info_msg("Something happened in ~p~n", [a_module]).
@@ -235,7 +235,7 @@ ok

Enables or disables printout of standard events to a file.

This is done by adding or deleting the standard event handler for output to file. Thus, calling this function overrides - the value of the Kernel error_logger configuration + the value of the Kernel error_logger configuration parameter.

Enabling file logging can be used together with calling tty(false), to have a silent system where @@ -274,7 +274,7 @@ ok to the terminal.

This is done by adding or deleting the standard event handler for output to the terminal. Thus, calling this function overrides - the value of the Kernel error_logger configuration parameter.

+ the value of the Kernel error_logger configuration parameter.

 @@ -323,7 +323,7 @@ ok The Format and Data arguments are the same as the arguments of io:format/2 - in STDLIB. + in STDLIB. The event is handled by the standard event handler. It is tagged as an error, warning, or info, see warning_map/0.

@@ -416,8 +416,8 @@ ok
See Also -

stdlib:gen_event(3), - stdlib:log_mf_h(3) +

gen_event(3), + log_mf_h(3) kernel(6) sasl(6)

diff --git a/lib/kernel/doc/src/file.xml b/lib/kernel/doc/src/file.xml index 7d86c3ebcb..d734ee25b8 100644 --- a/lib/kernel/doc/src/file.xml +++ b/lib/kernel/doc/src/file.xml @@ -79,7 +79,7 @@ list_dir_all/1 and read_link_all/1.

-

See also section Notes About Raw Filenames in the STDLIB User´s Giude.

+

See also section Notes About Raw Filenames in the STDLIB User´s Giude.

@@ -277,7 +277,7 @@ f.txt: {person, "kalle", 25}. {ok,[{person,"kalle",25},{person,"pelle",30}]}

The encoding of Filename can be set by a comment, as described in - stdlib:epp(3).

+ epp(3).

 @@ -445,7 +445,7 @@ f.txt: {person, "kalle", 25}.

The encoding of Filename can be set by a comment, as described in - stdlib:epp(3).

+ epp(3).

 @@ -455,7 +455,7 @@ f.txt: {person, "kalle", 25}.

The same as eval/1, but the variable bindings Bindings are used in the evaluation. For information about the variable bindings, see - stdlib:erl_eval(3).

+ erl_eval(3).

 @@ -830,7 +830,7 @@ f.txt: {person, "kalle", 25}. this module (file) for reading and writing data as the interfaces provided here work with byte-oriented data. Using other (Unicode) encodings makes the - stdlib:io(3) functions + io(3) functions get_chars, get_line, and put_chars more suitable, as they can work with the full Unicode range.

If data is sent to an io_device() in a format that cannot be @@ -847,7 +847,7 @@ f.txt: {person, "kalle", 25}. that is, read/2 are returned "as is". If module - stdlib:io(3) is used for + io(3) is used for writing, the file can only cope with Unicode characters up to code point 255 (the ISO Latin-1 range).

 @@ -861,7 +861,7 @@ f.txt: {person, "kalle", 25}. the file lies beyond the ISO Latin-1 range (0..255), but failure occurs if the data contains Unicode code points beyond that range. The file is best read with the functions in the Unicode aware module - stdlib:io(3).

+ io(3).

Bytes written to the file by any means are translated to UTF-8 encoding before being stored on the disk file.

@@ -891,7 +891,7 @@ f.txt: {person, "kalle", 25}. So a file can be analyzed in latin1 encoding for, for example, a BOM, positioned beyond the BOM and then be set for the right encoding before further reading. For functions identifying BOMs, see module - stdlib:unicode(3).

+ unicode(3).

This option is not allowed on raw files.

ram @@ -932,7 +932,7 @@ f.txt: {person, "kalle", 25}. closed and the process itself is terminated. An IoDevice returned from this call can be used as an argument to the I/O functions (see - stdlib:io(3)).

+ io(3)).

In previous versions of file, modes were specified as one of the atoms read, write, or @@ -1055,7 +1055,7 @@ f.txt: {person, "kalle", 25}.

The encoding of Filename can be set by a comment as described in - stdlib:epp(3).

+ epp(3).

@@ -1128,7 +1128,7 @@ f.txt: {person, "kalle", 25}.

The encoding of Filename can be set by a comment as described in - stdlib:epp(3).

+ epp(3).

 @@ -1389,7 +1389,7 @@ f.txt: {person, "kalle", 25}. {ok, FileInfo} if successful, otherwise {error, Reason}. FileInfo is a record - file_info, defined in the Kernel include file + file_info, defined in the Kernel include file file.hrl. Include the following directive in the module from which the function is called:

@@ -1552,7 +1552,7 @@ f.txt: {person, "kalle", 25}. raw line-oriented reading.

If encoding is set to something else than latin1, the read_line/1 call fails if the data contains characters larger than 255, - why module stdlib:io(3) is to be + why module io(3) is to be preferred when reading such a file.

The function returns:

@@ -1970,7 +1970,7 @@ f.txt: {person, "kalle", 25}.

Changes file information. Returns ok if successful, otherwise {error, Reason}. FileInfo is a record - file_info, defined in the Kernel include file + file_info, defined in the Kernel include file file.hrl. Include the following directive in the module from which the function is called:

diff --git a/lib/kernel/doc/src/gen_tcp.xml b/lib/kernel/doc/src/gen_tcp.xml index 83242c2df8..08454b9832 100644 --- a/lib/kernel/doc/src/gen_tcp.xml +++ b/lib/kernel/doc/src/gen_tcp.xml @@ -216,7 +216,7 @@ do_recv(Sock, Bs) -> time-out in milliseconds. Defaults to infinity.

The default values for options specified to connect can - be affected by the Kernel configuration parameter + be affected by the Kernel configuration parameter inet_default_connect_options. For details, see inet(3).

 @@ -293,7 +293,7 @@ do_recv(Sock, Bs) -> accept/1,2.

The default values for options specified to listen can - be affected by the Kernel configuration parameter + be affected by the Kernel configuration parameter inet_default_listen_options. For details, see inet(3).

 @@ -307,7 +307,7 @@ do_recv(Sock, Bs) -> See the description of HttpPacket in erlang:decode_packet/3 - in ERTS. + in ERTS.

Receives a packet from a socket in passive diff --git a/lib/kernel/doc/src/inet.xml b/lib/kernel/doc/src/inet.xml index 8cc21bf3e2..3f4e3684f4 100644 --- a/lib/kernel/doc/src/inet.xml +++ b/lib/kernel/doc/src/inet.xml @@ -36,7 +36,7 @@ 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 +

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 @@ -48,7 +48,7 @@

When accept is issued, the values of the listening socket options are inherited. No such application variable is therefore needed for accept.

-

Using the Kernel configuration parameters above, one +

Using the Kernel configuration parameters above, one can set default options for all TCP sockets on a node, but use this with care. Options such as {delay_send,true} can be specified in this way. The following is an example of starting an Erlang @@ -95,7 +95,7 @@ fe80::204:acff:fe17:bf38 -

The record is defined in the Kernel include file +

The record is defined in the Kernel include file "inet.hrl".

Add the following directive to the module:

@@ -391,7 +391,7 @@ get_tcpi_sacked(Sock) -> <<_:28/binary,TcpiSacked:32/native,_/binary>> = Info, TcpiSacked.]]>

Preferably, you would check the machine type, the operating system, - and the Kernel version before executing anything similar to + and the Kernel version before executing anything similar to this code.

 @@ -661,7 +661,7 @@ get_tcpi_sacked(Sock) ->

The size of the user-level software buffer used by the driver. Not to be confused with options sndbuf and recbuf, which correspond to the - Kernel socket buffers. It is recommended + Kernel socket buffers. It is recommended to have val(buffer) >= max(val(sndbuf),val(recbuf)) to avoid performance issues because of unnecessary copying. val(buffer) is automatically set to the above @@ -720,7 +720,7 @@ get_tcpi_sacked(Sock) ->

The socket message queue is set to a busy state when the amount of data on the message queue reaches this limit. Notice that this limit only - concerns data that has not yet reached the ERTS internal + concerns data that has not yet reached the ERTS internal socket implementation. Defaults to 8 kB.

Senders of data to the socket are suspended if either the socket message queue is busy or the socket @@ -736,7 +736,7 @@ get_tcpi_sacked(Sock) -> {high_watermark, Size} (TCP/IP sockets)

The socket is set to a busy state when the amount - of data queued internally by the ERTS socket implementation + of data queued internally by the ERTS socket implementation reaches this limit. Defaults to 8 kB.

Senders of data to the socket are suspended if either the socket message queue is busy or the socket @@ -816,7 +816,7 @@ get_tcpi_sacked(Sock) -> socket message queue is set in a not busy state when the amount of data queued in the message queue falls below this limit. Notice that this limit only concerns data - that has not yet reached the ERTS internal socket + that has not yet reached the ERTS internal socket implementation. Defaults to 4 kB.

Senders that are suspended because of either a busy message queue or a busy socket are resumed @@ -834,7 +834,7 @@ get_tcpi_sacked(Sock) ->

If the socket is in a busy state, the socket is set in a not busy state when the amount of data - queued internally by the ERTS socket implementation + queued internally by the ERTS socket implementation falls below this limit. Defaults to 4 kB.

Senders that are suspended because of a busy message queue or a busy socket are resumed @@ -954,7 +954,7 @@ setcap cap_sys_admin,cap_sys_ptrace,cap_dac_read_search+epi beam.smp are returned with the format according to HttpPacket described in - erlang:decode_packet/3 in ERTS. + erlang:decode_packet/3 in ERTS. A socket in passive mode returns {ok, HttpPacket} from gen_tcp:recv while an active socket sends messages like @@ -1130,7 +1130,7 @@ inet:setopts(Sock,[{raw,6,8,<<30:32/native>>}]),]]> can respond differently to this kind of option manipulation. Use with care.

Notice that the default options for TCP/IP sockets can be - changed with the Kernel configuration parameters mentioned in + changed with the Kernel configuration parameters mentioned in the beginning of this manual page.

diff --git a/lib/kernel/doc/src/init_stub.xml b/lib/kernel/doc/src/init_stub.xml index df89b174ca..1297c8264d 100644 --- a/lib/kernel/doc/src/init_stub.xml +++ b/lib/kernel/doc/src/init_stub.xml @@ -34,6 +34,6 @@ Coordination of system startup.

This module is moved to the - ERTS application.

+ ERTS application.

 diff --git a/lib/kernel/doc/src/kernel_app.xml b/lib/kernel/doc/src/kernel_app.xml index fb6421e1c5..df681a505f 100644 --- a/lib/kernel/doc/src/kernel_app.xml +++ b/lib/kernel/doc/src/kernel_app.xml @@ -31,12 +31,12 @@ kernel The Kernel application. -

The Kernel application has all the code necessary to run +

The Kernel application has all the code necessary to run the Erlang runtime system: file servers, code servers, and so on.

-

The Kernel application is the first application started. It is +

The Kernel application is the first application started. It is mandatory in the sense that the minimal system based on - Erlang/OTP consists of Kernel and STDLIB. Kernel + Erlang/OTP consists of Kernel and STDLIB. Kernel contains the following functional areas:

Start, stop, supervision, configuration, and distribution of applications @@ -53,13 +53,13 @@
Error Logger Event Handlers

Two standard error logger event handlers are defined in - the Kernel application. These are described in + the Kernel application. These are described in error_logger(3).

Configuration -

The following configuration parameters are defined for the Kernel +

The following configuration parameters are defined for the Kernel application. For more information about configuration parameters, see file app(4).

@@ -162,8 +162,8 @@ depth to which terms are printed by the error logger event handlers included in OTP. This configuration parameter is used by the two event handlers - defined by the Kernel application and the two event - handlers in the SASL application. + defined by the Kernel application and the two event + handlers in the SASL application. (If you have implemented your own error handlers, this configuration parameter has no effect on them.)

@@ -173,7 +173,7 @@ ~P and ~W, respectively, and Depth is used as the depth parameter. For details, see io:format/2 - in STDLIB.

+ in STDLIB.

A reasonable starting value for Depth is 30. We recommend to test crashing various processes in your @@ -241,7 +241,7 @@

The name (string) of an Inet user configuration file. For details, see section Inet Configuration - in the ERTS User's Guide.

+ in the ERTS User's Guide.

net_setuptime = SetupTime @@ -360,7 +360,7 @@ MaxT = TickTime + TickTime / 4 start_timer = true | false

Starts the timer_server if the parameter is - true (see stdlib:timer(3)). + true (see timer(3)). This parameter is to be set to true in an embedded system using this service.

Defaults to false.

diff --git a/lib/kernel/doc/src/net_kernel.xml b/lib/kernel/doc/src/net_kernel.xml index 3c1b3d5190..4e2b0c69db 100644 --- a/lib/kernel/doc/src/net_kernel.xml +++ b/lib/kernel/doc/src/net_kernel.xml @@ -55,7 +55,7 @@ $ erl -sname foobar erl.

Normally, connections are established automatically when another node is referenced. This functionality can be disabled - by setting Kernel configuration parameter + by setting Kernel configuration parameter dist_auto_connect to false, see kernel(6). In this case, connections must be established explicitly by calling @@ -146,7 +146,7 @@ $ erl -sname foobar are stopped. Two option lists are considered the same if they contain the same set of options.

-

As from Kernel version 2.11.4, and ERTS version +

As from Kernel version 2.11.4, and ERTS version 5.5.4, the following is guaranteed:

nodeup messages are delivered before delivery @@ -156,13 +156,13 @@ $ erl -sname foobar messages from the remote node that have been passed through the connection have been delivered.

 -

Notice that this is not guaranteed for Kernel +

Notice that this is not guaranteed for Kernel versions before 2.11.4.

-

As from Kernel version 2.11.4, subscriptions can also be +

As from Kernel version 2.11.4, subscriptions can also be made before the net_kernel server is started, that is, net_kernel:monitor_nodes/[1,2] does not return ignored.

-

As from Kernel version 2.13, and ERTS version +

As from Kernel version 2.13, and ERTS version 5.7, the following is guaranteed:

nodeup messages are delivered after the @@ -172,7 +172,7 @@ $ erl -sname foobar corresponding node has disappeared in results from erlang:nodes/X.

 -

Notice that this is not guaranteed for Kernel +

Notice that this is not guaranteed for Kernel versions before 2.13.

The format of the node status change messages depends on Options. If Options is diff --git a/lib/kernel/doc/src/notes.xml b/lib/kernel/doc/src/notes.xml index 3d35f6f57f..9e9be3f661 100644 --- a/lib/kernel/doc/src/notes.xml +++ b/lib/kernel/doc/src/notes.xml @@ -3482,7 +3482,7 @@ types (for instance, ensure_loaded/1 now only accepts an atom as documented; it used to accept a string too).

-

Dialyzer will generally emit warnings for any +

Dialyzer will generally emit warnings for any calls that use undocumented argument types. Even if the call happens to still work in R12B, you should correct your code. A future release will adhere to the diff --git a/lib/kernel/doc/src/rpc.xml b/lib/kernel/doc/src/rpc.xml index 8cad9fe4fc..5944e9321a 100644 --- a/lib/kernel/doc/src/rpc.xml +++ b/lib/kernel/doc/src/rpc.xml @@ -320,7 +320,7 @@ Information about a process.

Location transparent version of the BIF - erlang:process_info/1 in ERTS.

+ erlang:process_info/1 in ERTS.

@@ -330,7 +330,7 @@ Information about a process.

Location transparent version of the BIF - erlang:process_info/2 in ERTS.

+ erlang:process_info/2 in ERTS.

 diff --git a/lib/kernel/doc/src/zlib_stub.xml b/lib/kernel/doc/src/zlib_stub.xml index b111581b10..9ab9c4eb62 100644 --- a/lib/kernel/doc/src/zlib_stub.xml +++ b/lib/kernel/doc/src/zlib_stub.xml @@ -34,6 +34,6 @@ Zlib compression interface.

This module is moved to the - ERTS application.

+ ERTS application.

 -- cgit v1.2.3