From aff9b4210d0bbc151a1611e260417b0d76ee4a8d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= Date: Wed, 11 Jan 2017 14:41:34 +0100 Subject: errors.xml: Remove superfluous references to R10B --- system/doc/reference_manual/errors.xml | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'system/doc') 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.

A run-time error can also be emulated by calling - erlang:error(Reason) or erlang:error(Reason, Args) - (those appeared in Erlang 5.4/OTP-R10).

+ erlang:error(Reason) or erlang:error(Reason, Args).

A run-time error is another name for an exception of class error.

@@ -79,7 +78,6 @@

Exceptions are run-time errors or generated errors and are of three different classes, with different origins. The try expression - (new in Erlang 5.4/OTP R10B) can distinguish between the different classes, whereas the catch expression cannot. They are described in @@ -94,7 +92,7 @@ error Run-time error, for example, 1+a, or the process called - erlang:error/1,2 (new in Erlang 5.4/OTP R10B) + erlang:error/1,2 exit @@ -111,7 +109,7 @@ and a stack trace (which aids in finding the code location of the exception).

The stack trace can be retrieved using - erlang:get_stacktrace/0 (new in Erlang 5.4/OTP R10B) + erlang:get_stacktrace/0 from within a try expression, and is returned for exceptions of class error from a catch expression.

An exception of class error is also known as a run-time -- cgit v1.2.3