aboutsummaryrefslogtreecommitdiffstats
path: root/system
diff options
context:
space:
mode:
authorKostis Sagonas <[email protected]>2010-09-06 20:55:21 +0300
committerRaimo Niskanen <[email protected]>2010-09-07 09:18:12 +0200
commit730bb4644985cdcb163b9b32f90c4f0fc133c57e (patch)
tree306e56be8b307fcfe3e94cc65a6f8fd1653007b7 /system
parent57493ef46d92155f0f7223858c4b612b840f485a (diff)
downloadotp-730bb4644985cdcb163b9b32f90c4f0fc133c57e.tar.gz
otp-730bb4644985cdcb163b9b32f90c4f0fc133c57e.tar.bz2
otp-730bb4644985cdcb163b9b32f90c4f0fc133c57e.zip
Up-to-date additions and changes to type reference manual.
Diffstat (limited to 'system')
-rwxr-xr-xsystem/doc/reference_manual/typespec.xml28
1 files changed, 14 insertions, 14 deletions
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 @@
<section>
<title>Introduction of Types</title>
<p>
- 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.
</p>
<p>
- 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.
</p>
<p>
- Type information can be used to document function interfaces,
- provide more information for bug detection tools such as <c>Dialyzer</c>,
- and can be exploited by documentation tools such as <c>Edoc</c> 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 <c>@type</c> and
+ Type information can be used to document function interfaces,
+ provide more information for bug detection tools such as <c>Dialyzer</c>,
+ and can be exploited by documentation tools such as <c>Edoc</c> 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 <c>@type</c> and
<c>@spec</c> declarations used by <c>Edoc</c>.
</p>
<warning>
@@ -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.
</p>
</section>
@@ -462,7 +462,7 @@ mod:orddict(atom(), term())
-spec id(X) -> X when X :: tuple().
</pre>
<p>
- and provide bounded quantification. Currently, the <c>::</2> constraint
+ and provide bounded quantification. Currently, the <c>::</c> constraint
(the <c>is_subtype/2</c> guard) is the only guard constraint which can
be used in the <c>'when'</c> part of a <c>'-spec'</c> attribute.
</p>