From 730bb4644985cdcb163b9b32f90c4f0fc133c57e Mon Sep 17 00:00:00 2001
From: Kostis Sagonas
Date: Mon, 6 Sep 2010 20:55:21 +0300
Subject: Up-to-date additions and changes to type reference manual.
---
system/doc/reference_manual/typespec.xml | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
(limited to 'system/doc/reference_manual')
diff --git a/system/doc/reference_manual/typespec.xml b/system/doc/reference_manual/typespec.xml
index 981a44642a..29ec2ad78b 100755
--- a/system/doc/reference_manual/typespec.xml
+++ b/system/doc/reference_manual/typespec.xml
@@ -32,22 +32,22 @@
Introduction of Types
- Although Erlang is a dynamically typed language this section describes
- an extension to the Erlang language for declaring sets of Erlang terms
- to form a particular type, effectively forming a specific sub-type of the
- set of all Erlang terms.
+ Erlang is a dynamically typed language. Still, it comes with a
+ language extension for declaring sets of Erlang terms to form a
+ particular type, effectively forming a specific sub-type of the set
+ of all Erlang terms.
- Subsequently, these types can be used to specify types of record fields
- and the argument and return types of functions.
+ Subsequently, these types can be used to specify types of record fields
+ and the argument and return types of functions.
- Type information can be used to document function interfaces,
- provide more information for bug detection tools such as Dialyzer,
- and can be exploited by documentation tools such as Edoc for
- generating program documentation of various forms.
- It is expected that the type language described in this document will
- supersede and replace the purely comment-based @type and
+ Type information can be used to document function interfaces,
+ provide more information for bug detection tools such as Dialyzer,
+ and can be exploited by documentation tools such as Edoc for
+ generating program documentation of various forms.
+ It is expected that the type language described in this document will
+ supersede and replace the purely comment-based @type and
@spec declarations used by Edoc.
@@ -317,7 +317,7 @@ mod:orddict(atom(), term())
their defining module (i.e., only the module defining them is
allowed to depend on their term structure). Consequently, such
types do not make much sense as module local - module local
- types are anyway not accessible by other modules - and should
+ types are not accessible by other modules anyway - and should
always be exported.
@@ -462,7 +462,7 @@ mod:orddict(atom(), term())
-spec id(X) -> X when X :: tuple().
- and provide bounded quantification. Currently, the ::2> constraint
+ and provide bounded quantification. Currently, the :: constraint
(the is_subtype/2 guard) is the only guard constraint which can
be used in the 'when' part of a '-spec' attribute.
--
cgit v1.2.3