diff options
| author | Björn Gustavsson <[email protected]> | 2017-01-11 14:41:34 +0100 |
|---|---|---|
| committer | Björn Gustavsson <[email protected]> | 2017-01-11 14:50:19 +0100 |
| commit | aff9b4210d0bbc151a1611e260417b0d76ee4a8d (patch) | |
| tree | 444ebdede0f827b89bda709b6781206ee751fbc3 /system/doc | |
| parent | 19034aa8c9e9c1b24b91f4e1a73b9b09ffe1c92c (diff) | |
| download | otp-aff9b4210d0bbc151a1611e260417b0d76ee4a8d.tar.gz otp-aff9b4210d0bbc151a1611e260417b0d76ee4a8d.tar.bz2 otp-aff9b4210d0bbc151a1611e260417b0d76ee4a8d.zip | |
errors.xml: Remove superfluous references to R10B
Diffstat (limited to 'system/doc')
| -rw-r--r-- | system/doc/reference_manual/errors.xml | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/system/doc/reference_manual/errors.xml b/system/doc/reference_manual/errors.xml index e764cf431f..3e2d306561 100644 --- a/system/doc/reference_manual/errors.xml +++ b/system/doc/reference_manual/errors.xml @@ -49,8 +49,7 @@ The Erlang programming language has built-in features for handling of run-time errors.</p> <p>A run-time error can also be emulated by calling - <c>erlang:error(Reason)</c> or <c>erlang:error(Reason, Args)</c> - (those appeared in Erlang 5.4/OTP-R10).</p> + <c>erlang:error(Reason)</c> or <c>erlang:error(Reason, Args)</c>.</p> <p>A run-time error is another name for an exception of class <c>error</c>. </p> @@ -79,7 +78,6 @@ <p>Exceptions are run-time errors or generated errors and are of three different classes, with different origins. The <seealso marker="expressions#try">try</seealso> expression - (new in Erlang 5.4/OTP R10B) can distinguish between the different classes, whereas the <seealso marker="expressions#catch">catch</seealso> expression cannot. They are described in @@ -94,7 +92,7 @@ <cell align="left" valign="middle"><c>error</c></cell> <cell align="left" valign="middle">Run-time error, for example, <c>1+a</c>, or the process called - <c>erlang:error/1,2</c> (new in Erlang 5.4/OTP R10B)</cell> + <c>erlang:error/1,2</c></cell> </row> <row> <cell align="left" valign="middle"><c>exit</c></cell> @@ -111,7 +109,7 @@ and a stack trace (which aids in finding the code location of the exception).</p> <p>The stack trace can be retrieved using - <c>erlang:get_stacktrace/0</c> (new in Erlang 5.4/OTP R10B) + <c>erlang:get_stacktrace/0</c> from within a <c>try</c> expression, and is returned for exceptions of class <c>error</c> from a <c>catch</c> expression.</p> <p>An exception of class <c>error</c> is also known as a run-time |