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. --- erts/doc/src/absform.xml | 18 ++++---- erts/doc/src/alt_dist.xml | 10 ++--- erts/doc/src/communication.xml | 4 +- erts/doc/src/crash_dump.xml | 10 ++--- erts/doc/src/driver_entry.xml | 10 ++--- erts/doc/src/erl.xml | 86 +++++++++++++++++++------------------- erts/doc/src/erl_dist_protocol.xml | 10 ++--- erts/doc/src/erl_driver.xml | 20 ++++----- erts/doc/src/erl_ext_dist.xml | 10 ++--- erts/doc/src/erl_nif.xml | 6 +-- erts/doc/src/erl_prim_loader.xml | 14 +++---- erts/doc/src/erl_tracer.xml | 2 +- erts/doc/src/erlang.xml | 86 +++++++++++++++++++------------------- erts/doc/src/erlc.xml | 6 +-- erts/doc/src/erlsrv.xml | 2 +- erts/doc/src/erts_alloc.xml | 20 ++++----- erts/doc/src/escript.xml | 6 +-- erts/doc/src/inet_cfg.xml | 30 ++++++------- erts/doc/src/init.xml | 12 +++--- erts/doc/src/introduction.xml | 2 +- erts/doc/src/match_spec.xml | 14 +++---- erts/doc/src/notes.xml | 8 ++-- erts/doc/src/run_erl.xml | 2 +- erts/doc/src/start_erl.xml | 2 +- erts/doc/src/time_correction.xml | 10 ++--- 25 files changed, 200 insertions(+), 200 deletions(-) (limited to 'erts') diff --git a/erts/doc/src/absform.xml b/erts/doc/src/absform.xml index 174ad9c640..ab00d47425 100644 --- a/erts/doc/src/absform.xml +++ b/erts/doc/src/absform.xml @@ -41,21 +41,21 @@ - stdlib:epp(3) + epp(3) - stdlib:erl_eval(3) + erl_eval(3) - stdlib:erl_lint(3) + erl_lint(3) - sdlib:erl_parse(3) + erl_parse(3) - stdlib:erl_pp(3) + erl_pp(3) - stdlib:io(3) + io(3)

The functions are also used as input and output for parse transforms, see - the compiler:compile(3) + the compile(3) module.

We use the function Rep to denote the mapping from an Erlang source @@ -177,8 +177,8 @@ Representation of Parse Errors and End-of-File

In addition to the representations of forms, the list that represents a module declaration (as returned by functions in - stdlib:epp(3) and - sdlib:erl_parse(3)) + epp(3) and + erl_parse(3)) can contain the following:

diff --git a/erts/doc/src/alt_dist.xml b/erts/doc/src/alt_dist.xml index f3e3260230..be969a8267 100644 --- a/erts/doc/src/alt_dist.xml +++ b/erts/doc/src/alt_dist.xml @@ -40,7 +40,7 @@

The section is a step-by-step explanation of the example application (in the - Kernel application directory). The + Kernel application directory). The application implements distribution over Unix domain sockets and is written for the Sun Solaris 2 operating environment. The mechanisms are however general and apply to any operating system Erlang @@ -379,15 +379,15 @@ (line 40) can be used to implement an interface similar to Unix for output. The Erlang runtime system could previously not use outputv for the - distribution, but it can as from ERTS 5.7.2. - As this driver was written before ERTS 5.7.2 it does + distribution, but it can as from ERTS 5.7.2. + As this driver was written before ERTS 5.7.2 it does not use the outputv callback. Using the outputv callback is preferred, as it reduces copying of data. (We will however use scatter/gather I/O internally in the driver.)

-

As from ERTS 5.5.3 the driver interface was extended with +

As from ERTS 5.5.3 the driver interface was extended with version control and the possibility to pass capability information. - Capability flags are present on line 48. As from ERTS 5.7.4 flag + Capability flags are present on line 48. As from ERTS 5.7.4 flag ERL_DRV_FLAG_SOFT_BUSY is required for drivers that are to be used by the distribution. The soft busy flag implies that the diff --git a/erts/doc/src/communication.xml b/erts/doc/src/communication.xml index 632ca6c212..7e18a73aa8 100644 --- a/erts/doc/src/communication.xml +++ b/erts/doc/src/communication.xml @@ -89,9 +89,9 @@

Examples of major implementation changes:

- As from ERTS 5.5.2 exit signals to processes are truly + As from ERTS 5.5.2 exit signals to processes are truly asynchronously delivered. - As from ERTS 5.10 all signals from processes to ports + As from ERTS 5.10 all signals from processes to ports are truly asynchronously delivered. diff --git a/erts/doc/src/crash_dump.xml b/erts/doc/src/crash_dump.xml index d55ab222a7..a9aeb1888c 100644 --- a/erts/doc/src/crash_dump.xml +++ b/erts/doc/src/crash_dump.xml @@ -39,7 +39,7 @@

The Erlang crash dump had a major facelift in Erlang/OTP R9C. The information in this section is therefore not directly applicable for older dumps. However, if you use - observer:crashdump_viewer(3) on older dumps, + crashdump_viewer(3) on older dumps, the crash dumps are translated into a format similar to this.

@@ -57,7 +57,7 @@ cause is external limitations, such as running out of memory. A crash dump caused by an internal error can be caused by the system reaching limits in the emulator itself (like the number of atoms - in the system, or too many simultaneous ets tables). Usually the + in the system, or too many simultaneous ETS tables). Usually the emulator or the operating system can be reconfigured to avoid the crash, which is why interpreting the crash dump correctly is important.

@@ -133,7 +133,7 @@ Slogan: <reason> <Name>:<Name>/1 No function <Name>:start/2 -

The Kernel/STDLIB applications are +

The Kernel/STDLIB applications are damaged or the start script is damaged.

 Driver_select called with too large file descriptor @@ -199,7 +199,7 @@ Slogan: <reason> are still connected to an application failure. There is much more information available, so a thorough reading of the crash dump can reveal the crash reason. The size of processes, - the number of ets tables, and the Erlang data on each process + the number of ETS tables, and the Erlang data on each process stack can be useful to find the problem.

@@ -481,7 +481,7 @@ Slogan: <reason>
ETS Tables -

This section contains information about all the ets tables in +

This section contains information about all the ETS tables in the system. The following fields are of interest for each table:

diff --git a/erts/doc/src/driver_entry.xml b/erts/doc/src/driver_entry.xml index dea003f091..2421e0a8d9 100644 --- a/erts/doc/src/driver_entry.xml +++ b/erts/doc/src/driver_entry.xml @@ -4,7 +4,7 @@
- 20012015 + 20012016 Ericsson AB. All Rights Reserved. @@ -67,7 +67,7 @@ -

As from ERTS 5.9 (Erlang/OTP R15B) the driver interface +

As from ERTS 5.9 (Erlang/OTP R15B) the driver interface has been changed with larger types for the callbacks output, control, and @@ -78,7 +78,7 @@

Old drivers (compiled with an erl_driver.h from an - ERTS version earlier than 5.9) must be updated and have + ERTS version earlier than 5.9) must be updated and have to use the extended interface (with version management ).

@@ -481,7 +481,7 @@ typedef struct erl_drv_entry { although a driver instance has marked itself as busy (see erl_driver:set_busy_port). - As from ERTS 5.7.4 this flag is required for drivers used + As from ERTS 5.7.4 this flag is required for drivers used by the Erlang distribution (the behavior has always been required by drivers used by the distribution).

@@ -558,7 +558,7 @@ typedef struct erl_drv_entry { See Also

erl_driver(3), erlang(3), - kernel:erl_ddll(3)

+ erl_ddll(3)

diff --git a/erts/doc/src/erl.xml b/erts/doc/src/erl.xml index 1578d40ef8..f62d3fb170 100644 --- a/erts/doc/src/erl.xml +++ b/erts/doc/src/erl.xml @@ -46,7 +46,7 @@ you want to redirect standard input or output.

-

As from ERTS 5.9 (Erlang/OTP R15B) the runtime system does by +

As from ERTS 5.9 (Erlang/OTP R15B) the runtime system does by default not bind schedulers to logical processors. For more information, see system flag +sbt.

@@ -103,7 +103,7 @@ emulator flags. is an init flag, interpreted by . is a user flag, stored by - . It is read by Kernel and causes the + . It is read by Kernel and causes the Erlang runtime system to become distributed. Finally, everything after (that is, ) is considered as plain arguments.

@@ -143,9 +143,9 @@

Sets the application configuration parameter to the value for the application ; see - kernel:app(4) and + app(4) and - kernel:application(3).

+ application(3).

@@ -192,12 +192,12 @@ . Used when applications are installed in another directory than ; see - systools:make_script/1,2 in SASL.

+ systools:make_script/1,2 in SASL.

Enables the code path cache of the code server; see - kernel:code(3).

+ code(3).

 @@ -212,16 +212,16 @@

Specifies the name of a configuration file, , which is used to configure applications; see - kernel:app(4) and + app(4) and - kernel:application(3).

+ application(3).

If this flag is present, does not maintain a fully connected network of distributed Erlang nodes, and then global name registration cannot be used; see - kernel:global(3).

+ global(3).

 @@ -266,7 +266,7 @@

Starts heartbeat monitoring of the Erlang runtime system; see - kernel:heart(3).

+ heart(3).

 @@ -278,13 +278,13 @@ nodes are part of the result from on the other node. See also hidden global groups; - kernel:global_group(3).

+ global_group(3).

Specifies the IP addresses for the hosts on which Erlang boot servers are running, see - kernel:erl_boot_server(3). This flag + erl_boot_server(3). This flag is mandatory if flag is present.

The IP addresses must be specified in the standard form (four decimal numbers separated by periods, for example, @@ -338,7 +338,7 @@

Makes the Erlang runtime system invoke in the current working directory and then terminate; see - tools:make(3). Implies + make(3). Implies .

 @@ -351,7 +351,7 @@

Indicates if the system is to load code dynamically (), or if all code is to be loaded during system initialization (); see - kernel:code(3). + code(3). Defaults to .

 @@ -359,7 +359,7 @@

Makes the Erlang runtime system into a distributed node. This flag invokes all network servers necessary for a node to become distributed; see - kernel:net_kernel(3). It is also ensured that + net_kernel(3). It is also ensured that runs on the current host before Erlang is started; see epmd(1).and the -start_epmd option.

@@ -383,7 +383,7 @@

Disables the sticky directory facility of the Erlang code server; see - kernel:code(3).

+ code(3).

 @@ -394,23 +394,23 @@

Adds the specified directories to the beginning of the code path, similar to ; see - kernel:code(3). + code(3). As an alternative to -pa, if several directories are to be prepended to the code path and the directories have a common parent directory, that parent directory can be specified in environment variable ERL_LIBS; see - kernel:code(3).

+ code(3).

Adds the specified directories to the end of the code path, similar to ; see - kernel:code(3).

+ code(3).

Replaces the path specified in the boot script; see - sasl:script(4).

+ script(4).

 @@ -436,7 +436,7 @@

Specifies an alternative to for starting a slave node on a remote host; see - stdlib:slave(3).

+ slave(3).

 (init flag) @@ -612,11 +612,11 @@ -

Sets the maximum number of ets tables.

+

Sets the maximum number of ETS tables.

 -

Forces option compressed on all ets tables. +

Forces option compressed on all ETS tables. Only intended for test and evaluation.

 @@ -627,11 +627,11 @@ code points > 255.

For more information about Unicode filenames, see section Unicode - Filenames in the STDLIB User's Guide. Notice that + Filenames in the STDLIB User's Guide. Notice that this value also applies to command-line parameters and environment variables (see section - Unicode in Enviroment and Parameters in the STDLIB + Unicode in Enviroment and Parameters in the STDLIB User's Guide).

 @@ -663,11 +663,11 @@ points to an invalid filename.

For more information about Unicode filenames, see section Unicode - Filenames in the STDLIB User's Guide. Notice that + Filenames in the STDLIB User's Guide. Notice that this value also applies to command-line parameters and environment variables (see section - Unicode in Enviroment and Parameters in the STDLIB + Unicode in Enviroment and Parameters in the STDLIB User's Guide).

@@ -684,11 +684,11 @@ selected, then w, i, or e have no effect.

For more information about Unicode filenames, see section Unicode - Filenames in the STDLIB User's Guide. Notice that + Filenames in the STDLIB User's Guide. Notice that this value also applies to command-line parameters and environment variables (see section - Unicode in Enviroment and Parameters in the STDLIB + Unicode in Enviroment and Parameters in the STDLIB User's Guide).

@@ -783,7 +783,7 @@ example, your font does not cover all Unicode characters.

See also - io:printable_range/0 in STDLIB.

+ io:printable_range/0 in STDLIB.

@@ -838,7 +838,7 @@ -

Forces ets memory block to be moved on realloc.

+

Forces ETS memory block to be moved on realloc.

 @@ -1268,7 +1268,7 @@

Enables or disables eager check I/O scheduling. Defaults to true. The default was changed from false - as from ERTS 7.0. The behavior before this + as from ERTS 7.0. The behavior before this flag was introduced corresponds to +secio false.

The flag effects when schedulers will check for I/O operations possible to execute, and when such I/O operations @@ -1365,7 +1365,7 @@ +sws default|legacy

Sets scheduler wakeup strategy. Default strategy changed in - ERTS 5.10 (Erlang/OTP R16A). This strategy was known as + ERTS 5.10 (Erlang/OTP R16A). This strategy was known as proposal in Erlang/OTP R15. The legacy strategy was used as default from R13 up to and including R15.

@@ -1446,7 +1446,7 @@ The current mapping can be retrieved using . For more information, see - error_logger:warning_map/0 in Kernel.

+ error_logger:warning_map/0 in Kernel.

 @@ -1515,7 +1515,7 @@ , the runtime system waits indefinitely for the crash dump file to be written.

This variable is used with - kernel:heart(3) if heart is running:

+ heart(3) if heart is running:

Suppresses the writing a crash dump file entirely, thus @@ -1558,7 +1558,7 @@

Contains a list of additional library directories that the code server searches for applications and adds to the code path; see - kernel:code(3).

+ code(3).

 @@ -1631,14 +1631,14 @@ code:load_abs("..../user_default"). ]]> erts_alloc(3), init(3), - kernel:application(3), - kernel:auth(3), - kernel:code(3), + application(3), + auth(3), + code(3), - kernel:erl_boot_server(3), - kernel:heart(3), - kernel:net_kernel(3), - tools:make(3)

+ erl_boot_server(3), + heart(3), + net_kernel(3), + make(3)

diff --git a/erts/doc/src/erl_dist_protocol.xml b/erts/doc/src/erl_dist_protocol.xml index a5949ce15f..ee74983730 100644 --- a/erts/doc/src/erl_dist_protocol.xml +++ b/erts/doc/src/erl_dist_protocol.xml @@ -5,7 +5,7 @@
2007 - 2015 + 2016 Ericsson AB, All Rights Reserved @@ -48,7 +48,7 @@

Authentication (done by - kernel:net_kernel(3)) (3)

+ net_kernel(3)) (3)

Connected (4)

@@ -573,7 +573,7 @@ io:format("old/unused name ~ts at port ~p, fd = ~p ~n",

Every message in the handshake starts with a 16-bit big-endian integer, which contains the message length (not counting the two initial bytes). In Erlang this corresponds to option {packet, 2} in - kernel:gen_tcp(3). + gen_tcp(3). Notice that after the handshake, the distribution switches to 4 byte packet headers.

@@ -825,7 +825,7 @@ DiB == gen_digest(ChA, ICA)?
Protocol between Connected Nodes -

As from ERTS 5.7.2 the runtime system passes a distribution flag +

As from ERTS 5.7.2 the runtime system passes a distribution flag in the handshake stage that enables the use of a distribution header on all messages passed. Messages passed between nodes have in @@ -869,7 +869,7 @@ DiB == gen_digest(ChA, ICA)? number is omitted from the terms that follow a distribution header .

-

Nodes with an ERTS version earlier than 5.7.2 does not pass the +

Nodes with an ERTS version earlier than 5.7.2 does not pass the distribution flag that enables the distribution header. Messages passed between nodes have in this case the following format:

diff --git a/erts/doc/src/erl_driver.xml b/erts/doc/src/erl_driver.xml index 8e83b74986..836a58a676 100644 --- a/erts/doc/src/erl_driver.xml +++ b/erts/doc/src/erl_driver.xml @@ -71,7 +71,7 @@ -

As from ERTS 5.5.3 the driver interface has been extended +

As from ERTS 5.5.3 the driver interface has been extended (see extended marker). The extended interface introduces version management, @@ -81,7 +81,7 @@ initialization, and some new driver API functions.

-

As from ERTS 5.9 old drivers must be recompiled +

As from ERTS 5.9 old drivers must be recompiled and use the extended interface. They must also be adjusted to the 64-bit capable driver interface.

@@ -406,7 +406,7 @@
Rewrites for 64-Bit Driver Interface -

ERTS 5.9 introduced two new integer types, +

ERTS 5.9 introduced two new integer types, ErlDrvSizeT and ErlDrvSSizeT, which can hold 64-bit sizes if necessary.

@@ -423,7 +423,7 @@ to get better warnings. Try to find a similar flag if you use another compiler.

-

The following is a checklist for rewriting a pre ERTS 5.9 driver, +

The following is a checklist for rewriting a pre ERTS 5.9 driver, most important first:

@@ -717,7 +717,7 @@ typedef struct ErlDrvBinary {

Notice that as a driver binary is shared by the driver and the emulator. A binary received from the emulator or sent to the emulator must not be changed by the driver.

-

Since ERTS 5.5 (Erlang/OTP R11B), orig_bytes is +

Since ERTS 5.5 (Erlang/OTP R11B), orig_bytes is guaranteed to be properly aligned for storage of an array of doubles (usually 8-byte aligned).

@@ -1058,7 +1058,7 @@ r = driver_async(myPort, &myKey, myData, myFunc); ]]>

The return value is -1 if the driver_async call fails.

-

As from ERTS 5.5.4.3 the default stack size for +

As from ERTS 5.5.4.3 the default stack size for threads in the async-thread pool is 16 kilowords, that is, 64 kilobyte on 32-bit architectures. This small default size has been chosen because the @@ -2534,11 +2534,11 @@ ERL_DRV_MAP int sz

The unsigned integer data type ErlDrvUInt and the signed integer data type ErlDrvSInt are 64 bits wide on a 64-bit runtime system and 32 bits wide on a 32-bit - runtime system. They were introduced in ERTS 5.6 + runtime system. They were introduced in ERTS 5.6 and replaced some of the int arguments in the list above.

The unsigned integer data type ErlDrvUInt64 and the signed integer data type ErlDrvSInt64 are always 64 bits - wide. They were introduced in ERTS 5.7.4.

+ wide. They were introduced in ERTS 5.7.4.

To build the tuple {tcp, Port, [100 | Binary]}, the following call can be made.

ERL_DRV_BINARY and the ErlDrvBinary in question.

The ERL_DRV_UINT, ERL_DRV_BUF2BINARY, and ERL_DRV_EXT2TERM term types were introduced in - ERTS 5.6.

+ ERTS 5.6.

This function is only thread-safe when the emulator with SMP support is used.

@@ -3213,7 +3213,7 @@ erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0] See Also

driver_entry(3), erlang(3), - kernel:erl_ddll(3), + erl_ddll(3), section How to Implement an Alternative Carrier for the Erlang Distribution> in the User's Guide

diff --git a/erts/doc/src/erl_ext_dist.xml b/erts/doc/src/erl_ext_dist.xml index fed41098f8..4f799f8f34 100644 --- a/erts/doc/src/erl_ext_dist.xml +++ b/erts/doc/src/erl_ext_dist.xml @@ -5,7 +5,7 @@
2007 - 2015 + 2016 Ericsson AB, All Rights Reserved @@ -119,7 +119,7 @@ Compressed Data Format when Expanded -

As from ERTS 5.10 (OTP R16) support +

As from ERTS 5.10 (OTP R16) support for UTF-8 encoded atoms has been introduced in the external format. However, only characters that can be encoded using Latin-1 (ISO-8859-1) are currently supported in atoms. The support for UTF-8 encoded atoms @@ -149,9 +149,9 @@ Distribution Header

- As from ERTS 5.7.2 the old atom cache protocol was + As from ERTS 5.7.2 the old atom cache protocol was dropped and a new one was introduced. This protocol - introduced the distribution header. Nodes with an ERTS version + introduced the distribution header. Nodes with an ERTS version earlier than 5.7.2 can still communicate with new nodes, but no distribution header and no atom cache are used.

@@ -799,7 +799,7 @@

- SMALL_ATOM_EXT was introduced in ERTS 5.7.2 and + SMALL_ATOM_EXT was introduced in ERTS 5.7.2 and require an exchange of distribution flag DFLAG_SMALL_ATOM_TAGS in the diff --git a/erts/doc/src/erl_nif.xml b/erts/doc/src/erl_nif.xml index 4ec5ab78d8..b5dc9037c4 100644 --- a/erts/doc/src/erl_nif.xml +++ b/erts/doc/src/erl_nif.xml @@ -474,7 +474,7 @@ return term; register/unregister its name, and so on.

Termination of a process executing a dirty NIF can only be completed up to a certain point while it executes the dirty NIF. - All Erlang resources, such as its registered name and its ets + All Erlang resources, such as its registered name and its ETS tables, are released. All links and monitors are triggered. The execution of the NIF is, however, not stopped. The NIF can safely continue execution, allocate heap memory, and so on, @@ -1573,7 +1573,7 @@ typedef enum { enif_raise_exception.

-

Before ERTS 7.0 (Erlang/OTP 18), the return value +

Before ERTS 7.0 (Erlang/OTP 18), the return value from enif_make_badarg had to be returned from the NIF. This requirement is now lifted as the return value from the NIF is ignored if enif_make_badarg has been invoked.

@@ -2561,7 +2561,7 @@ enif_map_iterator_destroy(env, &iter); thread.

Passing msg_env as NULL is only supported as from - ERTS 8.0 (Erlang/OTP 19).

+ ERTS 8.0 (Erlang/OTP 19).

 diff --git a/erts/doc/src/erl_prim_loader.xml b/erts/doc/src/erl_prim_loader.xml index 86a3b98eda..286bac6c93 100644 --- a/erts/doc/src/erl_prim_loader.xml +++ b/erts/doc/src/erl_prim_loader.xml @@ -60,7 +60,7 @@ for example, $OTPROOT/lib/mnesia-4.4.7.ez/mnesia-4.4.7/ebin/mnesia.beam. For information about archive files, see - kernel:code(3).

+ code(3).

@@ -87,7 +87,7 @@ for example, $OTPROOT/lib/mnesia-4.4.7.ez/mnesia-4.4.7/ebin. For information about archive files, see - kernel:code(3).

+ code(3).

@@ -98,18 +98,18 @@

Retrieves information about a file. Returns {ok, FileInfo} if successful, otherwise error. 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:

-include_lib("kernel/include/file.hrl").

For more information about the record file_info, see - kernel:file(3).

+ file(3).

Filename can also be a file in an archive, for example, $OTPROOT/lib/mnesia-4.4.7.ez/mnesia-4.4.7/ebin/mnesia. For information about archive files, see - kernel:code(3).

+ code(3).

@@ -167,7 +167,7 @@ can use. This flag is mandatory if flag -loader inet is present. On each host, there must be on Erlang node with the - kernel:erl_boot_server(3), + erl_boot_server(3), which handles the load requests. Hosts is a list of IP addresses (hostnames are not acceptable).

@@ -184,7 +184,7 @@ See Also

init(3), - kernel:erl_boot_server(3)

+ erl_boot_server(3)

diff --git a/erts/doc/src/erl_tracer.xml b/erts/doc/src/erl_tracer.xml index 131157eef8..83eef374ca 100644 --- a/erts/doc/src/erl_tracer.xml +++ b/erts/doc/src/erl_tracer.xml @@ -434,7 +434,7 @@ specified.

For more information on what Label and SeqTraceInfo can be, see - kernel:seq_trace(3).

+ seq_trace(3).

diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml index 18f1b2e833..d0a3a77e43 100644 --- a/erts/doc/src/erlang.xml +++ b/erts/doc/src/erlang.xml @@ -377,7 +377,7 @@ Z = erlang:adler32_combine(X,Y,iolist_size(Data2)). 2> binary_part(Bin,{0,2}). <<1,2>>

For details about the PosLen semantics, see - stdlib:binary(3).

+ binary(3).

Allowed in guard tests.

@@ -504,7 +504,7 @@ Z = erlang:adler32_combine(X,Y,iolist_size(Data2)). this function is deprecated. New code is to use binary:bin_to_list/3 - in STDLIB instead. All functions in module + in STDLIB instead. All functions in module binary consistently use zero-based indexing.

@@ -724,7 +724,7 @@ Z = erlang:adler32_combine(X,Y,iolist_size(Data2)).

Returns true if Module has old code, otherwise false.

See also - kernel:code(3).

+ code(3).

@@ -825,7 +825,7 @@ Z = erlang:adler32_combine(X,Y,iolist_size(Data2)).

See also - kernel:code(3).

+ code(3).

Failures:

badarg @@ -1051,7 +1051,7 @@ Z = erlang:crc32_combine(X,Y,iolist_size(Data2)). otherwise true.

This BIF is intended for the code server (see - kernel:code(3)) + code(3)) and is not to be used elsewhere.

Failure: badarg if there already is an old version of @@ -2519,7 +2519,7 @@ os_prompt%

This BIF is intended for the code server (see - kernel:code(3)) + code(3)) and is not to be used elsewhere.

@@ -2584,7 +2584,7 @@ os_prompt%

Returns a list of all loaded Erlang modules (current and old code), including preloaded modules.

See also - kernel:code(3).

+ code(3).

@@ -2864,7 +2864,7 @@ os_prompt% ets -

The total amount of memory currently allocated for ets +

The total amount of memory currently allocated for ETS tables. This memory is part of the memory presented as system memory.

 @@ -2885,7 +2885,7 @@ os_prompt%

For information on how to run the emulator with instrumentation, see - tools:instrument(3) + instrument(3) and/or erl(1).

 @@ -2933,7 +2933,7 @@ RealSystem = system + MissedSystem memory blocks.

-

As from ERTS 5.6.4, erlang:memory/0 requires that +

As from ERTS 5.6.4, erlang:memory/0 requires that all erts_alloc(3) allocators are enabled (default behavior).

 @@ -2954,7 +2954,7 @@ RealSystem = system + MissedSystem of memory_type() atoms, in which case a corresponding list of {memory_type(), Size :: integer >= 0} tuples is returned.

-

As from ERTS 5.6.4, +

As from ERTS 5.6.4, erlang:memory/1 requires that all erts_alloc(3) allocators are enabled (default behavior).

@@ -3002,7 +3002,7 @@ RealSystem = system + MissedSystem the module.

This BIF is intended for the code server (see - kernel:code(3)) + code(3)) and is not to be used elsewhere.

 @@ -3225,13 +3225,13 @@ RealSystem = system + MissedSystem time-out for the monitored node to connect itself, even if it cannot be actively connected from this node (that is, it is blocked). The state where this can be useful - can only be achieved by using the Kernel option + can only be achieved by using the Kernel option dist_auto_connect once. If that option is not used, option allow_passive_connect has no effect.

Option allow_passive_connect is used internally and is seldom needed in applications where the - network topology and the Kernel options in effect + network topology and the Kernel options in effect are known in advance.

Failure: badarg if the local node is not alive or the @@ -3297,9 +3297,9 @@ RealSystem = system + MissedSystem

Works exactly like error/1, but - Dialyzer thinks that this BIF will return an arbitrary + Dialyzer thinks that this BIF will return an arbitrary term. When used in a stub function for a NIF to generate an - exception when the NIF library is not loaded, Dialyzer + exception when the NIF library is not loaded, Dialyzer does not generate false warnings.

@@ -3310,9 +3310,9 @@ RealSystem = system + MissedSystem

Works exactly like error/2, but - Dialyzer thinks that this BIF will return an arbitrary + Dialyzer thinks that this BIF will return an arbitrary term. When used in a stub function for a NIF to generate an - exception when the NIF library is not loaded, Dialyzer + exception when the NIF library is not loaded, Dialyzer does not generate false warnings.

 @@ -3435,9 +3435,9 @@ RealSystem = system + MissedSystem translation or to force, for example UTF-8, supply the executable and/or arguments as a binary in the correct encoding. For details, see the module - kernel:file(3), the + file(3), the function - file:native_name_encoding/0 in Kernel, and + file:native_name_encoding/0 in Kernel, and the Using Unicode in Erlang User's Guide.

@@ -3749,7 +3749,7 @@ RealSystem = system + MissedSystem the owning process using signals of the form {'EXIT', Port, PosixCode}. For the possible values of PosixCode, see - kernel:file(3).

+ file(3).

The maximum number of ports that can be open at the same time can be configured by passing command-line flag +Q to @@ -3764,7 +3764,7 @@ RealSystem = system + MissedSystem

Portable hash function that gives the same hash for the same Erlang term regardless of machine architecture and - ERTS version (the BIF was introduced in ERTS 4.9.1.1). + ERTS version (the BIF was introduced in ERTS 4.9.1.1). The function returns a hash value for Term within the range 1..Range. The maximum value for @@ -3784,7 +3784,7 @@ RealSystem = system + MissedSystem

Portable hash function that gives the same hash for the same Erlang term regardless of machine architecture and - ERTS version (the BIF was introduced in ERTS 5.2). + ERTS version (the BIF was introduced in ERTS 5.2). The function returns a hash value for Term within the range 0..Range-1. The maximum value for @@ -4347,7 +4347,7 @@ RealSystem = system + MissedSystem Information about the queue size of a port.

Bytes is the total number - of bytes queued by the port using the ERTS driver queue + of bytes queued by the port using the ERTS driver queue implementation.

If the port identified by Port is not open, undefined is returned. If the port is closed and the @@ -4573,7 +4573,7 @@ RealSystem = system + MissedSystem

All messages in the message queue will eventually be placed on heap. They can however temporarily be stored off heap. This is how messages always have been stored - up until ERTS 8.0.

+ up until ERTS 8.0.

The default message_queue_data process flag is determined @@ -5153,11 +5153,11 @@ RealSystem = system + MissedSystem that no processes execute old code in the module.

This BIF is intended for the code server (see - kernel:code(3)) + code(3)) and is not to be used elsewhere.

 -

As from ERTS 8.0 (Erlang/OTP 19), any lingering processes +

As from ERTS 8.0 (Erlang/OTP 19), any lingering processes that still execute the old code is killed by this function. In earlier versions, such incorrect use could cause much more fatal failures, like emulator crash.

@@ -6056,7 +6056,7 @@ true

If Dest is a pid(), the timer is automatically canceled if the process referred to by the pid() is not alive, or if the process exits. This - feature was introduced in ERTS 5.4.11. Notice that + feature was introduced in ERTS 5.4.11. Notice that timers are not automatically canceled when Dest is an atom().

See also @@ -6157,7 +6157,7 @@ true system flag microstate_accounting.

statistics(microstate_accounting) returns a list of maps - representing some of the OS threads within ERTS. Each map + representing some of the OS threads within ERTS. Each map contains type and id fields that can be used to identify what thread it is, and also a counters field that contains data about how @@ -6249,7 +6249,7 @@ lists:map( scheduler_wall_time fraction. Without extra states this time is part of the other state. ets - Time spent executing ets BIFs. Without extra states + Time spent executing ETS BIFs. Without extra states this time is part of the emulator state. gc_full Time spent doing fullsweep garbage collection. Without extra @@ -6265,7 +6265,7 @@ lists:map( part of the other state.

The utility module - runtime_tools:msacc(3) + msacc(3) can be used to more easily analyse these statistics.

Returns undefined if system flag @@ -6288,7 +6288,7 @@ lists:map( 

 > statistics(reductions).
 {2046,11}
-

As from ERTS 5.5 (Erlang/OTP R11B), +

As from ERTS 5.5 (Erlang/OTP R11B), this value does not include reductions performed in current time slices of currently scheduled processes. If an exact value is wanted, use @@ -7107,7 +7107,7 @@ ok

Returns a list of the names of all allocators using - the ERTS internal alloc_util framework + the ERTS internal alloc_util framework as atoms. For more information, see section The alloc_util framework @@ -7117,7 +7117,7 @@ ok

Returns information about the specified allocator. - As from ERTS 5.6.1, the return value is a list + As from ERTS 5.6.1, the return value is a list of {instance, InstanceNo, InstanceInfo} tuples, where InstanceInfo contains information about a specific instance of the allocator. @@ -7134,8 +7134,8 @@ ok

The recognized allocators are listed in erts_alloc(3). Information about super carriers can be obtained from - ERTS 8.0 with {allocator, erts_mmap} or from - ERTS 5.10.4; the returned list when calling with + ERTS 8.0 with {allocator, erts_mmap} or from + ERTS 5.10.4; the returned list when calling with {allocator, mseg_alloc} also includes an {erts_mmap, _} tuple as one element in the list.

After reading the erts_alloc(3) documentation, @@ -7619,7 +7619,7 @@ ok (for example, ./configure --with-dynamic-trace=dtrace). For more information about dynamic tracing, see - runtime_tools:dyntrace(3) manual page and the + dyntrace(3) manual page and the README.dtrace/README.systemtap files in the Erlang source code top directory.

@@ -7659,7 +7659,7 @@ ok ets_limit -

Returns the maximum number of ets tables allowed. This +

Returns the maximum number of ETS tables allowed. This limit can be increased at startup by passing command-line flag +e to @@ -7847,7 +7847,7 @@ ok

Returns a string containing the OTP release number of the - OTP release that the currently executing ERTS application + OTP release that the currently executing ERTS application is part of.

As from Erlang/OTP 17, the OTP release number corresponds to the major OTP version number. No @@ -8222,7 +8222,7 @@ ok tolerant_timeofday -

Returns whether a pre ERTS 7.0 backwards compatible +

Returns whether a pre ERTS 7.0 backwards compatible compensation for sudden changes of system time is enabled or disabled. Such compensation is enabled when the time offset @@ -8290,8 +8290,8 @@ ok

Argument scheduler has changed name to scheduler_id to avoid mix up with argument schedulers. Argument scheduler was - introduced in ERTS 5.5 and renamed in - ERTS 5.5.1.

+ introduced in ERTS 5.5 and renamed in + ERTS 5.5.1.

 @@ -9451,7 +9451,7 @@ timestamp() ->

The delivery of trace messages (generated by erlang:trace/3, - kernel:seq_trace(3), + seq_trace(3), or erlang:system_profile/2) is dislocated on the time-line diff --git a/erts/doc/src/erlc.xml b/erts/doc/src/erlc.xml index ca3412b72c..7355be488b 100644 --- a/erts/doc/src/erlc.xml +++ b/erts/doc/src/erlc.xml @@ -303,9 +303,9 @@ erlc +export_all file.erl

See Also

erl(1), - compiler:compile(3), - parsetools:yecc(3), - snmp:snmp(3)

+ compile(3), + yecc(3), + snmp(3)

diff --git a/erts/doc/src/erlsrv.xml b/erts/doc/src/erlsrv.xml index 53583b625d..6c08b25220 100644 --- a/erts/doc/src/erlsrv.xml +++ b/erts/doc/src/erlsrv.xml @@ -527,7 +527,7 @@ void initialize_handler(void){ See Also

start_erl(1), - sasl:release_handler(3)

+ release_handler(3)

diff --git a/erts/doc/src/erts_alloc.xml b/erts/doc/src/erts_alloc.xml index a43f51b10a..8ab35851c1 100644 --- a/erts/doc/src/erts_alloc.xml +++ b/erts/doc/src/erts_alloc.xml @@ -246,7 +246,7 @@ If it satisfies the request, it is used, otherwise a new carrier is created. The implementation has a time complexity that is constant.

-

As from ERTS 5.6.1 the emulator refuses to +

As from ERTS 5.6.1 the emulator refuses to use this strategy on other allocators than temp_alloc. This because it only causes problems for other allocators.

@@ -454,7 +454,7 @@ enabled) is passed instead of a ]]>, a recomended non-zero utilization value is used. The value chosen depends on the allocator type and can be changed between - ERTS versions. Defaults to de, but this + ERTS versions. Defaults to de, but this can be changed in the future.

Carriers are abandoned when memory utilization in the allocator instance falls below the @@ -617,7 +617,7 @@ SMP support is NoSchedulers+1 instances. Each scheduler uses a lock-free instance of its own and other threads use a common instance.

-

Before ERTS 5.9 it was possible to configure +

Before ERTS 5.9 it was possible to configure a smaller number of thread-specific instances than schedulers. This is, however, not possible anymore.

@@ -688,7 +688,7 @@

A map over current allocations is kept by the emulator. The allocation map can be retrieved through module - tools:instrument(3). +Mim true + instrument(3). +Mim true implies +Mis true. +Mim true is the same as flag -instr in erl(1).

@@ -698,7 +698,7 @@

Status over allocated memory is kept by the emulator. The allocation status can be retrieved through module - tools:instrument(3).

+ instrument(3).

+Mit X @@ -737,10 +737,10 @@

Disables features that cannot be enabled while creating an allocator configuration with - runtime_tools:erts_alloc_config(3).

+ erts_alloc_config(3).

This option is to be used only while running - runtime_tools:erts_alloc_config(3), not when + erts_alloc_config(3), not when using the created configuration.

 @@ -780,7 +780,7 @@

The - runtime_tools:erts_alloc_config(3) + erts_alloc_config(3) tool can be used to aid creation of an erts_alloc configuration that is suitable for a limited number of runtime scenarios.

@@ -791,9 +791,9 @@

erl(1), erlang(3), - runtime_tools:erts_alloc_config(3), + erts_alloc_config(3), - tools:instrument(3)

+ instrument(3)

diff --git a/erts/doc/src/escript.xml b/erts/doc/src/escript.xml index 602b88f6ed..1d5d280338 100644 --- a/erts/doc/src/escript.xml +++ b/erts/doc/src/escript.xml @@ -4,7 +4,7 @@
- 20072015 + 20072016 Ericsson AB. All Rights Reserved. @@ -101,7 +101,7 @@ io:setopts([{encoding, unicode}]) is latin1, as the script runs in a non-interactive terminal (see section - Summary of Options) in the STDLIB User's Guide.

+ Summary of Options) in the STDLIB User's Guide.

On the third line (or second line depending on the presence of the Emacs directive), arguments can be specified to @@ -193,7 +193,7 @@ halt(1). as one of the emulator flags. Module must be the name of a module that has an exported main/1 function. For more information about archives and code loading, see - kernel:code(3).

+ code(3).

It is often very convenient to have a header in the escript, especially on Unix platforms. However, the header is optional, so you directly can "execute" diff --git a/erts/doc/src/inet_cfg.xml b/erts/doc/src/inet_cfg.xml index 3b104a0032..0cfcc7905d 100644 --- a/erts/doc/src/inet_cfg.xml +++ b/erts/doc/src/inet_cfg.xml @@ -40,7 +40,7 @@ for specific settings for Erlang to function properly on a correctly IP-configured platform.

-

When Erlang starts up it reads the Kernel variable +

When Erlang starts up it reads the Kernel variable , which, if defined, is to specify the location and name of a user configuration file. Example:

@@ -57,7 +57,7 @@ -

Notice that the Kernel variable +

Notice that the Kernel variable overrides this environment variable.

If no user configuration file is specified and Erlang is started @@ -68,7 +68,7 @@ /etc/host.conf and /etc/nsswitch.conf) in these modes, except for /etc/resolv.conf and /etc/hosts that is read and monitored for changes on Unix platforms for the internal DNS client - kernel:inet_res(3).

+ inet_res(3).

If Erlang is started in long name distributed mode, it needs to get the domain name from somewhere and reads system inet @@ -138,7 +138,7 @@

Specify a system file that Erlang is to read resolver configuration from for the internal DNS client - kernel:inet_res(3), + inet_res(3), and monitor for changes, even if it does not exist. The path must be absolute.

This can override the configuration parameters @@ -200,7 +200,7 @@

Add address (and port, if other than default) of the primary nameserver to use for - kernel:inet_res(3). + inet_res(3).

@@ -209,14 +209,14 @@

Add address (and port, if other than default) of the secondary nameserver for - kernel:inet_res(3). + inet_res(3).

Add search domains for - kernel:inet_res(3). + inet_res(3).

@@ -229,7 +229,7 @@ (use host data retrieved from system configuration files and/or the user configuration file) (use the Erlang DNS client - kernel:inet_res(3) + inet_res(3) for nameserver queries)

The lookup method tries to @@ -249,7 +249,7 @@

Set how often (in milliseconds) the resolver cache for - kernel:inet_res(3) + inet_res(3) is refreshed (that is, expired DNS records are deleted). Defaults to 1 hour.

@@ -258,28 +258,28 @@

Set the time to wait until retry (in milliseconds) for DNS queries made by - kernel:inet_res(3). + inet_res(3). Defaults to 2 seconds.

Set the number of DNS queries - kernel:inet_res(3) + inet_res(3) will try before giving up. Defaults to 3.

Tells the DNS client - kernel:inet_res(3) + inet_res(3) to look up IPv6 addresses. Defaults to false.

Tells the DNS client - kernel:inet_res(3) + inet_res(3) to use TCP (Virtual Circuit) instead of UDP. Defaults to false.

 @@ -287,7 +287,7 @@

Sets the EDNS version that - kernel:inet_res(3) + inet_res(3) will use. The only allowed version is zero. Defaults to false, which means not to use EDNS.

 @@ -295,7 +295,7 @@

Sets the allowed UDP payload size - kernel:inet_res(3) + inet_res(3) will advertise in EDNS queries. Also sets the limit when the DNS query will be deemed too large for UDP forcing a TCP query instead; this is not entirely diff --git a/erts/doc/src/init.xml b/erts/doc/src/init.xml index 54507c6572..c14f0a558d 100644 --- a/erts/doc/src/init.xml +++ b/erts/doc/src/init.xml @@ -42,7 +42,7 @@

init reads the boot script, which contains instructions on how to initiate the system. For more information about boot scripts, see - sasl:script(4).

+ script(4).

init also contains functions to restart, reboot, and stop the system.

@@ -154,7 +154,7 @@ terminates. If command-line flag -heart was specified, the heart program tries to reboot the system. For more information, see - kernel:heart(3).

+ heart(3).

To limit the shutdown time, the time init is allowed to spend taking down applications, command-line flag -shutdown_time is to be used.

@@ -207,7 +207,7 @@ command-line flag -heart was specified, the heart program is terminated before the Erlang node terminates. For more information, see - kernel:heart(3).

+ heart(3).

To limit the shutdown time, the time init is allowed to spend taking down applications, command-line flag -shutdown_time is to be used.

@@ -254,9 +254,9 @@ useful when you want to elaborate with code loading from archives without editing the boot script. For more information about interpretation of boot scripts, see - sasl:script(4). + script(4). The flag has also a similar effect on how the code server works; see - kernel:code(3).

+ code(3).

 -epmd_module Module @@ -361,7 +361,7 @@ error
See Also

erl_prim_loader(3), - kernel:heart(3)

+ heart(3)

diff --git a/erts/doc/src/introduction.xml b/erts/doc/src/introduction.xml index 97a0d5999e..790e24f9f3 100644 --- a/erts/doc/src/introduction.xml +++ b/erts/doc/src/introduction.xml @@ -34,7 +34,7 @@
Scope -

The Erlang Runtime System Application, ERTS, contains +

The Erlang Runtime System Application, ERTS, contains functionality necessary to run the Erlang system.

By default, is only guaranteed to be diff --git a/erts/doc/src/match_spec.xml b/erts/doc/src/match_spec.xml index 1b297c5d29..2a14f1e47b 100644 --- a/erts/doc/src/match_spec.xml +++ b/erts/doc/src/match_spec.xml @@ -142,7 +142,7 @@

A match specification used in - stdlib:ets(3) + ets(3) can be described in the following informal grammar:

@@ -678,7 +678,7 @@

If the match specification is executed when selecting objects - from an ets table:

+ from an ETS table:

Evaluate the expressions in order and return the value of the last expression (typically there is only one expression in this context).

@@ -691,11 +691,11 @@
Differences between Match Specifications in ETS and Tracing -

ets match specifications produce a return value. +

ETS match specifications produce a return value. Usually the contains one single that defines the return value without any side effects. Calls with side effects are not allowed in - the ets context.

+ the ETS context.

When tracing there is no return value to produce, the match specification either matches or does not. The effect when the @@ -824,7 +824,7 @@

ETS Examples -

Match all objects in an ets table, where the first element is +

Match all objects in an ETS table, where the first element is the atom 'strider' and the tuple arity is 3, and return the whole object:

@@ -834,7 +834,7 @@ ['$_']}] ]]> -

Match all objects in an ets table with arity > 1 and the first +

Match all objects in an ETS table with arity > 1 and the first element is 'gandalf', and return element 2:

Function ets:test_ms/2> - can be useful for testing complicated ets matches.

+ can be useful for testing complicated ETS matches.

diff --git a/erts/doc/src/notes.xml b/erts/doc/src/notes.xml index ca3f654c36..2a36e5568c 100644 --- a/erts/doc/src/notes.xml +++ b/erts/doc/src/notes.xml @@ -9380,9 +9380,9 @@ dynamically linking against libssl.so and libcrypto.so. The runtime library search path has also been extended. The configure - scripts of erl_interface and odbc now + scripts of Erl_interface and ODBC now search for thread libraries and thread library quirks the - same way as erts do. The + same way as ERTS do. The configure script of the odbc application now also looks for odbc libraries in lib64 and lib/64 directories when building on a 64-bit @@ -10498,7 +10498,7 @@

- A corrected bug in ets for bag and + A corrected bug in ETS for bag and duplicate_bag. A delete/2 or lookup_element/3 could miss objects in a fixed table if one or more objects with the same key had @@ -10940,7 +10940,7 @@

- A corrected bug in ets for bag and + A corrected bug in ETS for bag and duplicate_bag. A delete/2 or lookup_element/3 could miss objects in a fixed table if one or more objects with the same key had diff --git a/erts/doc/src/run_erl.xml b/erts/doc/src/run_erl.xml index 4780c00ea4..ad7b2c5b85 100644 --- a/erts/doc/src/run_erl.xml +++ b/erts/doc/src/run_erl.xml @@ -174,7 +174,7 @@ without Daylight Saving Time), rather than in local time. This does not affect data coming from Erlang, only the logs output directly by run_erl. Application - SASL can be modified accordingly by setting the Erlang + SASL can be modified accordingly by setting the Erlang application variable to .

 diff --git a/erts/doc/src/start_erl.xml b/erts/doc/src/start_erl.xml index 50f8c58a48..4887d4606e 100644 --- a/erts/doc/src/start_erl.xml +++ b/erts/doc/src/start_erl.xml @@ -163,7 +163,7 @@ See Also

erlsrv(1), - sasl:release_handler(3)

+ release_handler(3)

diff --git a/erts/doc/src/time_correction.xml b/erts/doc/src/time_correction.xml index 8042ad3b99..77e7a40529 100644 --- a/erts/doc/src/time_correction.xml +++ b/erts/doc/src/time_correction.xml @@ -4,7 +4,7 @@
- 19992015 + 19992016 Ericsson AB. All Rights Reserved. @@ -35,7 +35,7 @@
New Extended Time Functionality -

As from Erlang/OTP 18 (ERTS 7.0) the time functionality +

As from Erlang/OTP 18 (ERTS 7.0) the time functionality has been extended. This includes a new API for time and @@ -247,7 +247,7 @@ everything that has anything to do with time. All timers, regardless of it is a receive ... after timer, BIF timer, or a timer in the - stdlib:timer(3) + timer(3) module, are triggered relative Erlang monotonic time. Even Erlang system time is based on Erlang monotonic time. @@ -408,7 +408,7 @@ and does not change later. This is the default behavior, but not because it is the best mode (which it is not). It is default only because this is how the runtime system - behaved until ERTS 7.0. + behaved until ERTS 7.0. Ensure that your Erlang code that can execute during a time warp is time warp safe before enabling other modes.

@@ -663,7 +663,7 @@
New Erlang Monotonic Time -

Erlang monotonic time as such is new as from ERTS 7.0. +

Erlang monotonic time as such is new as from ERTS 7.0. It is introduced to detach time measurements, such as elapsed time from calendar time. In many use cases there is a need to measure elapsed time or specify a time relative to another point -- cgit v1.2.3