Ulrich's fixes to documentation.
This commit is contained in:
12
docs/swi.tex
12
docs/swi.tex
@@ -299,7 +299,7 @@ is not an atom, a type error is raised.
|
||||
Delete the named attribute. If @var{Var} loses its last attribute it
|
||||
is transformed back into a traditional Prolog variable. If @var{Module}
|
||||
is not an atom, a type error is raised. In all other cases this
|
||||
predicate succeeds regarless whether or not the named attribute is
|
||||
predicate succeeds regardless of whether or not the named attribute is
|
||||
present.
|
||||
|
||||
@item attr_unify_hook(+@var{AttValue},+@var{VarValue})
|
||||
@@ -385,7 +385,7 @@ terms. They differ in various ways from storing information using
|
||||
consider module scoping in future versions.
|
||||
@end itemize
|
||||
|
||||
Both @code{b_setval/2} and @code{nb_setval/2} implicitely create a variable if the
|
||||
Both @code{b_setval/2} and @code{nb_setval/2} implicitly create a variable if the
|
||||
referenced name does not already refer to a variable.
|
||||
|
||||
Global variables may be initialised from directives to make them
|
||||
@@ -437,10 +437,10 @@ initial value other than @code{[]} prior to backtrackable assignment.
|
||||
@snindex nb_getval/2
|
||||
@cnindex nb_getval/2
|
||||
The @code{nb_getval/2} predicate is a synonym for b_getval/2, introduced for
|
||||
compatibility and symetry. As most scenarios will use a particular
|
||||
global variable either using non-backtracable or backtrackable
|
||||
compatibility and symmetry. As most scenarios will use a particular
|
||||
global variable either using non-backtrackable or backtrackable
|
||||
assignment, using @code{nb_getval/2} can be used to document that the
|
||||
variable is used non-backtracable.
|
||||
variable is used non-backtrackable.
|
||||
|
||||
@c \predicate{nb_linkval}{2}{+Name, +Value}
|
||||
@c Associates the term @var{Value} with the atom @var{Name} without copying
|
||||
@@ -448,7 +448,7 @@ variable is used non-backtracable.
|
||||
@c expert users only because the semantics on backtracking to a point
|
||||
@c before creating the link are poorly defined for compound terms. The
|
||||
@c principal term is always left untouched, but backtracking behaviour on
|
||||
@c arguments is undone if the orginal assignment was \jargon{trailed} and
|
||||
@c arguments is undone if the original assignment was \jargon{trailed} and
|
||||
@c left alone otherwise, which implies that the history that created the
|
||||
@c term affects the behaviour on backtracking. Please consider the
|
||||
@c following example:
|
||||
|
Reference in New Issue
Block a user