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/erl_driver.xml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'erts/doc/src/erl_driver.xml') 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

-- cgit v1.2.3