Screamer was originally written by Jeffrey Mark Siskind and David Allen McAllester.
The copy of Screamer this documentation refers to is maintained courtesy of Steel Bank Studio Ltd by Nikodemus Siivola.
The Google Group
http://groups.google.com/group/screamer/
exists for Screamer-related discussions.
Screamer is maintained in Git:
git clone git://github.com/nikodemus/screamer.git
will get you a local copy.
http://github.com/nikodemus/screamer
is the GitHub project page.
NOTE: This documentation is a work in progress. In the meanwhile you may wish to refer to the original papers below.
Following original publications by Siskind and McAllester form the basis of this manual:
Screaming Yellow Zonkers, 1991. Old Screamer manual, doesn't always hold true for Screamer 3.20 on which this “modern” Screamer is based, but still probably the most complete discussion of various operators.
Screamer: A Portable Efficient Implementation of Nondeterministic Common Lisp, 1993. A paper describing the fundamentals of Screamer.
Nondeterministic Lisp as a Substrate for Constraint Logic Programming, 1993. A paper describing the constaints propagation features of Screamer.
Screamer shadows defun.
Examples in this manual are expected to be entered in the package
SCREAMER-USER, which has the correct defun.
Packages using Screamer are best defined using
define-screamer-package, which is like defpackage but
does some additional shadowing imports.
This is however by no means necessary: you can also explicitly use
screamer::defun.
Screamer adds nondeterminism by providing the choice-point
operator either and the failure operator fail.
A choice-point is a point in program where more than one thing can happen. When a choice point is encountered, one of the possibilities occurs, and execution continues. Should a failure subsequently occur, the system backtracks to the last choice-point where multiple possibilities were still present, and tries again.
(all-values
(let ((x (either 1 2 3 4)))
(if (oddp x)
x
(fail)))) ; => (1 3)
At first (either 1 2 3 4) evaluates to 1, which is oddp,
so all-values receives it and sets about producing the next
value.
This time either returns 2, which isn't oddp. Hence
fail is called causing the system to backtrack.
Starting again from the choice-point 3 is produced, which is
oddp, and is received by all-values, which in turn
requests the next value.
Now either returns 4, which again causes fail to backtrack.
Since the only choice-point available cannot produce any more alternatives,
control passes back to all-values which returns the collected values.
Had we wanted only one answer instead of an enumeration of all
possible answers we could have used one-value instead of
all-values.
If you're familiar with Prolog, all-values and one-value
are analogous to Prolog's bag-of and cut primitives.
Given either and fail we can write functions returning
arbitrary sequences of nondeterministic values. Such functions are
called generators, and by convention have names starting with
a- or an-.
Consider for example an-integer-between:
;;; Screamer already provides an-integer-between, so we'll
;;; call this by a different name.
(defun an-int-between (min max)
(if (> min max)
(fail)
(either min (an-int-between (1+ min) max))))
(all-values (an-int-between 41 43)) ; => (41 42 43)
Called with two integers, this function produces nondeterministic values in the given range – finally backtracking to a previous choice-point when possibilities have already been exhausted.
Given an-integer-between and fail we can write eg. a
generator for square numbers:
;;; Square numbers are numbers produced by multiplying an integer with itself.
(defun a-square-number (min max)
(let* ((x (an-integer-between 0 max))
(square (* x x)))
(if (<= min square max)
square
(fail))))
(all-values (a-square-number 12 80)) ; => (16 25 36 49 64)
We're not restricted to numbers, of course. Writing a generator for potential comedy duos works just the same:
(defun a-comedic-actor ()
(list (either :tall :short) (either :thin :fat)))
(defun a-comedy-duo ()
(let ((a (a-comedic-actor))
(b (a-comedic-actor)))
(if (or (eq (first a) (first b))
(eq (second a) (second b)))
(fail)
(list a :and b))))
(one-value (a-comedy-duo)) ; => ((:TALL :THIN) :AND (:SHORT :FAT))
What should happen to side-effects when a nondeterministic function backtracks? It depends. Some side-effects should be retained, and some undone – and it is impossible for the system to know in general what is the right choice in a given case.
Screamer is able to undo effects of setf and setq
(including calls to user-defined setf-functions), but cannot undo
calls to other functions with side-effects such as set,
rplaca, or sort.
By default most side-effects are retained:
(let ((n 0))
(list :numbers
(all-values (let ((x (an-integer-between 0 3)))
(incf n)
x))
:n n)) ; => (:NUMBERS (0 1 2 3) :N 4)
Macros local and global can be used to turn undoing of
side-effects on and off lexically.
(let ((m 0)
(n 0))
(list :numbers
(all-values (let ((x (an-integer-between 0 3)))
(local
(incf n)
(global
(incf m)))
x))
:m m
:n n)) ; => (:NUMBERS (0 1 2 3) :M 4 :N 0)
In addition to nondeterminism via backtracking as discussed so far,
Screamer also provides for forward constraint propagation via
logic variables constructed using make-variable.
Screamer provides a variety of primitives for constraining variables.
By convention suffix v is used to denote operators that accept
(and potentially return) variables in addition to values. Any
foov is generally just like foo, except its arguments
can also be logic variables, and that it may assert facts about them
and will possibly return another variable.
The operator assert! is the primary tool about asserting facts
about variables.
Expression such as (foov myvar) typically returns another
variable depending on myvar, which can be constrained to be
true using assert!.
;;; Make a variable
(defparameter *v* (make-variable "The Answer"))
;;; It is initially unconstrained.
*v* ; => ["The Answer"]
;;; Constrain it to be an integer.
(assert! (integerpv *v*))
*v* ; => ["The Answer" integer]
;;; Constrain 40 to be 2 less than *v*
(assert! (=v 40 (-v *v* 2)))
;;; And we have our answer.
*v* ; => 42
Assertions – and constraint operators in general – can cause failure and backtracking, in which case constraints from the last attempt are undone.
This allows us to search the solution space using backtracking:
(defparameter *x* (make-variable "X"))
(defparameter *y* (make-variable "Y"))
(assert! (integerpv *x*))
(assert! (integerpv *y*))
(assert! (=v 0 (+v *x* *y* 42)))
(all-values (let ((x (an-integer-between -50 -30))
(y (an-integer-between 2 5)))
(assert! (=v *x* x))
(assert! (=v *y* y))
(list x y))) ; => ((-47 5) (-46 4) (-45 3) (-44 2))
A possibly less intuitive, but usually more efficient method is to assert range constraints as variables instead of nondeterministic values, and force a solution:
(assert! (=v *x* (an-integer-betweenv -50 -30)))
(assert! (=v *y* (an-integer-betweenv 2 5)))
(all-values
(solution (list *x* *y*)
(static-ordering #'linear-force))) => ((-47 5) (-46 4) (-45 3) (-44 2))
In this case backtracking occurs only inside solution, when the
system is trying to apply different solution to the given constraints,
whereas in the first one we backtracked over the entire let.
Screamer is implemented using a code-walker, which does not unfortunately currently support the full ANSI Common Lisp.
Following special operators signal an error if they appear in code processed by the code walker:
Following special operators are accepted, but they cannot contain nondeterministic forms:
Additionally, functions defined using flet and labels
are not in nondeterministic context, even if the surrounding context
is nondeterministic.
Undoing side-effects via local is reliable only if the
setf and setq forms are lexically apparent:
(local (incf (foo)))
may or may not work as expected, depending on how foo is
implemented. If (incf (foo)) expands using eg. set-foo,
the code-walker will not notice the side-effect.
Undoing side-effects via local when there is no prior value
might not work as expected, depending on the implementation of the
place:
local will cause that to happen.
Example: assignment to an unbound variable inside local signals
an error.
nil) to be returned, undoing the side-effect means assigning
the marker object back to the place.
Example: undoing (setf gethash) of a previously unknown key
will cause nil to be stored in the table instead of removing
the new key and its value entirely via remhash.
Solving the “Einstein's Riddle” using nondeterministic features of Screamer, ie. backtracking search.
Solving the “The Zebra Puzzle”, using forward constraint propagation features of Screamer.
(This puzzle is virtually identical to “Einstein's Riddle”, but the solution is very different.)
Nondeterministically evaluates and returns the value of one of its
expressions.
eithertakes any number of arguments. With no arguments,(either)is equivalent to(fail)and is thus deterministic. With one argument,(either expression)is equivalent to expression itself and is thus deterministic only whenexpressionis deterministic. With two or more argument it is nondeterministic and can only appear in a nondeterministic context.It sets up a choice point and evaluates the first
expressionreturning its result. Whenever backtracking proceeds to this choice point, the nextexpressionis evaluated and its result returned. When no moreexpressionsremain, the current choice point is removed and backtracking continues to the next most recent choice point.As an optimization, the choice point created for this expression is removed before the evaluation of the last
expressionso that a failure during the evaluation of the last expression will backtrack directly to the parent choice point of theeitherexpression.
eitheris a special form, not a function. It is an error for the expression#'eitherto appear in a program.
Backtracks to the most recent choise point. Equivalent to
(either). Note thatfailis deterministic function and thus it is permissible to reference#'fail, and write(funcall #'fail)or(apply #'fail). In nondeterministic contexts, the expression(fail)is optimized to generate inline backtracking code.
Evaluates
expressionsas an implicitprognand returns a list of all of the nondeterministic values returned by the lastexpression.These values are produced by repeatedly evaluating the body and backtracking to produce the next value, until the body fails and yields no further values.
Accordingly, local side effects performed by the body while producing each value are undone before attempting to produce subsequent values, and all local side effects performed by the body are undone upon exit from
all-values.Returns the list containing
nilif there are noexpressions. Anall-valuesexpression can appear in both deterministic and nondeterministic contexts. Irrespective of what context theall-valuesexpression appears in, theexpressionsare always in a nondeterministic context. Anall-valuesexpression itself is always deterministic.all-valuesis analogous to the bagof primitive in Prolog.
Returns the first value of a nondeterministic expression.
expressionis evaluated, deterministically returning only its first nondeterministic value, if any.No further execution of
expressionis attempted after it successfully returns one value.If
expressiondoes not return any nondeterministic values (i.e. it fails) thendefault-expressionis evaluated and its value returned instead.default-expressiondefaults to(fail)if not present.Local side effects performed by
expressionare undone whenone-valuereturns, but local side effects performed bydefault-expressionare not undone whenone-valuereturns.A
one-valueexpression can appear in both deterministic and nondeterministic contexts. Irrespective of what context theone-valueexpression appears in,expressionis always in a nondeterministic context, whiledefault-expressionis in whatever context theone-valueexpression appears.A
one-valueexpression is nondeterministic ifdefault-expressionis present and is nondeterministic, otherwise it is deterministic.If
default-expressionis present and nondeterministic, and ifexpressionfails, then it is possible to backtrack into thedefault-expressionand for theone-valueexpression to nondeterministically return multiple times.one-valueis analogous to the cut primitive(!)in Prolog.
Evaluates
formsas an implicitprognin a nondeterministic context and returnsnil.The body is repeatedly backtracked to its first choice-point until the body fails.
Local side effects performed by
formsare undone whenfor-effectsreturns.A
for-effectsexpression can appear in both deterministic and nondeterministic contexts. Irrespective of what context thefor-effectsexpression appears in,formsare always in a nondeterministic context.A
for-effectsexpression is is always deterministic.
Returns the Ith value of a nondeterministic expression.
expressionis evaluated, deterministically returning only its Ith nondeterministic value, if any. I must be an integer. The first nondeterministic value returned byexpressionis numbered zero, the second one, etc. The Ith value is produced by repeatedly evaluatingexpression, backtracking through and discarding the first I values and deterministically returning the next value produced.No further execution of
expressionis attempted after it successfully returns the desired value.If
expressionfails before returning both the I values to be discarded, as well as the desired Ith value, thendefault-expressionis evaluated and its value returned instead.default-expressiondefaults to(fail)if not present.Local side effects performed by
expressionare undone whenith-valuereturns, but local side effects performed bydefault-expressionand by I are not undone whenith-valuereturns.An
ith-valueexpression can appear in both deterministic and nondeterministic contexts. Irrespective of what context theith-valueexpression appears in,expressionis always in a nondeterministic context, whiledefault-expressionand I are in whatever context theith-valueexpression appears.An
ith-valueexpression is nondeterministic ifdefault-expressionis present and is nondeterministic, or if I is nondeterministic. Otherwise it is deterministic.If
default-expressionis present and nondeterministic, and ifexpressionfails, then it is possible to backtrack into thedefault-expressionand for theith-valueexpression to nondeterministically return multiple times.If I is nondeterministic then the
ith-valueexpression operates nondeterministically on each value of I. In this case, backtracking for each value ofexpressionanddefault-expressionis nested in, and restarted for, each backtrack of I.
Evaluates
expressionsas an implicitprognand prints each of the nondeterministic values returned by the lastexpressionin succession usingAfter each value is printed, the user is queried as to whether or not further values are desired. These values are produced by repeatedly evaluating the body and backtracking to produce the next value, until either the user indicates that no further values are desired or until the body fails and yields no further values.
Accordingly, local side effects performed by the body while producing each value are undone after printing each value, before attempting to produce subsequent values, and all local side effects performed by the body are undone upon exit from
print-values, either because there are no further values or because the user declines to produce further values.A
print-valuesexpression can appear in both deterministic and nondeterministic contexts. Irrespective of what context theprint-valuesexpression appears in, theexpressionsare always in a nondeterministic context. Aprint-valuesexpression itself is always deterministic and always returnsnil.
print-valuesis analogous to the standard top-level user interface in Prolog.
Evaluates
formsas an implicitprognin nondeterministic context, returning true if the body ever yields true.The body is repeatedly backtracked as long as it yields
nil. Returns the first true value yielded by the body, ornilif body fails before yielding true.Local side effects performed by the body are undone when
possibly? returns.A
possibly? expression can appear in both deterministic and nondeterministic contexts. Irrespective of what context thepossibly? expression appears in, its body is always in a nondeterministic context.A
possibly? expression is always deterministic.
Evaluates
formsas an implicitprognin nondeterministic context, returning true if the body never yields false.The body is repeatedly backtracked as long as it yields true. Returns the last true value yielded by the body if it fails before yielding
nil, otherwise returnsnil.Local side effects performed by the body are undone when
necessarily? returns.A
necessarily? expression can appear in both deterministic and nondeterministic contexts. Irrespective of what context thenecessarily? expression appears in, its body is always in a nondeterministic context.A
necessarily? expression is always deterministic.
Evaluates
expressionsin the same fashion asprognexcept that allsetfandsetqexpressions lexically nested in its body result in global side effects which are not undone upon backtracking.Note that this affects only side effects introduced explicitly via
setfandsetq. Side effects introduced by Common Lisp builtin functions such asrplacaare always global anyway.Furthermore, it affects only occurrences of
setfandsetqwhich appear textually nested in the body of theglobalexpression--not those appearing in functions called from the body.
localandglobalexpressions may be nested inside one another. The nearest surrounding declaration determines whether or not a givensetforsetqresults in a local or global side effect.Side effects default to be global when there is no surrounding
localorglobalexpression. Global side effects can appear both in deterministic as well as nondeterministic contexts. In nondeterministic contexts,globalas well assetfare treated as special forms rather than macros. This should be completely transparent to the user.
Evaluates
expressionsin the same fashion asprognexcept that allsetfandsetqexpressions lexically nested in its body result in local side effects which are undone upon backtracking.This affects only side effects introduced explicitly via
setfandsetq. Side effects introduced by either user defined functions or builtin Common Lisp functions such asrplacaare always global.Behaviour of side effects introduced by macro-expansions such as
incfdepends on the exact macro-expansion. If(incf (foo))expands using eg.set-foo,localis unable to undo the side-effect.
localdoes not currently distinguish between initially uninitialized and intialized places, such as unbound variables or hash-table keys with no prior values. As a result, an attempt to assign an unbound variable insidelocalwill signal an error due to the system's attempt to first read the variable. Similarly, undoing a(setf gethash)when the key did not previously exist in the table will insert anilinto the table instead of doing aremhash.
localandglobalexpressions may be nested inside one another. The nearest surrounding declaration determines whether or not a givensetforsetqresults in a local or global side effect.Side effects default to be global when there is no surrounding
localorglobalexpression. Local side effects can appear both in deterministic as well as nondeterministic contexts though different techniques are used to implement the trailing of prior values for restoration upon backtracking. In nondeterministic contexts,localas well assetfare treated as special forms rather than macros. This should be completely transparent to the user.
Nondeterministically returns an element of
sequence. The elements are returned in the order that they appear insequence. Thesequencemust be either a list or a vector.
Generator yielding integers starting from
lowand continuing sequentially in increasing direction.
Generator yielding integers starting from
highand continuing sequentially in decreasing direction.
Nondeterministically returns an integer in the closed interval [
low,high]. The results are returned in ascending order. Bothlowandhighmust be integers. Fails if the interval does not contain any integers.
Analogous to the
cl:apply, exceptfunctioncan be either a nondeterministic function, or an ordinary deterministic function.You must use
apply-nondeterministicto apply a nondeterministic function. An error is signalled if a nondeterministic function object is used withcl:apply.You can use
apply-nondeterministicto apply either a deterministic or nondeterministic function, though even if all of theargumentsare deterministic andfunctionis a deterministic function object, the call expression will still be nondeterministic (with presumably a single value), since it is impossible to determine at compile time that a given call toapply-nondeterministicwill be passed only deterministic function objects for function.
Analogous to
cl:funcall, exceptfunctioncan be either a nondeterministic function, or an ordinary determinisitic function.You must use
funcall-nondeterministicto funcall a nondeterministic function. An error is signalled if you attempt to funcall a nondeterministic function object withcl:funcall.You can use
funcall-nondeterministicto funcall either a deterministic or nondeterministic function, though even if all of theargumentsare deterministic andfunctionis a deterministic function object, the call expression will still be nondeterministic (with presumably a single value), since it is impossible to determine at compile time that a given call tofuncall-nondeterministicwill be passed only deterministic function objects for function.
Analogous to the
cl:multiple-value-call, exceptfunction-formcan evaluate to either a nondeterministic function, or an ordinary deterministic function.You must use
multiple-value-call-nondeterministicto multiple-value-call a nondeterministic function. An error is signalled if a nondeterministic function object is used withcl:multiple-value-call.You can use
multiple-value-call-nondeterministicto call either a deterministic or nondeterministic function, though even if all of thevalues-formsare deterministic andfunction-formevaluates to a deterministic function object, the call expression will still be nondeterministic (with presumably a single value), since it is impossible to determine at compile time that a given call tomultiple-value-call-nondeterministicwill be passed only deterministic function objects for function.While
multiple-value-call-nondeterministicappears to be a function, it is really a special-operator implemented by the code-walkers processing nondeterministic source contexts.
Returns
tifxis a nondeterministic function andnilotherwise.
#'fooreturns a nondeterministic function object iff it is used in nondeterminisitc context andfoois either a nondeterministiclambdaform, or the name of a nondeterministic function defined usingscreamer::defun.Currently, if
foois a nondeterministic function defined usingscreamer::defun,#'fooand(symbol-function 'foo)in deterministic context will return an ordinary deterministic Common Lisp function, which will signal an error at runtime.
Creates and returns a new variable. Variables are assigned a name which is only used to identify the variable when it is printed. If the parameter
nameis given then it is assigned as the name of the variable. Otherwise, a unique name is assigned. The parameternamecan be any Lisp object.
Returns
xifxis not a variable. Ifxis a variable thenvalue-ofdereferencesxand returns the dereferenced value. Ifxis bound then the value returned will not be a variable. Ifxis unbound then the value returned will be a variable which may bexitself or another variable which is shared withx.
Returns
tifxis not a variable or ifxis a bound variable. Otherwise returnsnil.bound? is analogous to the extra-logical predicatesvarandnonvartypically available in Prolog.
The primitive
ground? is an extension of the primitivebound? which can recursively determine whether an entire aggregate object is bound. Returnstifxis bound and either the value ofxis atomic or all of the slots in the value ofxare also bound. Otherwise returns nil.
Restricts
xtot. No meaningful result is returned. The argumentxcan be either a variable or a non-variable.This assertion may cause other assertions to be made due to noticers attached to
x.A call to
assert! fails ifxis known not to equaltprior to the assertion or if any of the assertions performed by the noticers result in failure.Except for the fact that one cannot write
#'assert!,assert! behaves like a function, even though it is implemented as a macro.The reason it is implemented as a macro is to allow a number of compile time optimizations. Expressions like
(assert! (notv x)),(assert! (numberpv x))and(assert! (notv (numberv x)))are transformed into calls to functions internal to Screamer which eliminate the need to create the boolean variable(s) normally returned by functions likenotvandnumberpv. Calls to the functionsnumberpv,realpv,integerpv,memberv,booleanpv,=v,<v,<=v,>v,>=v,/=v,notv,funcallv,applyvandequalvwhich appear directly nested in a call toassert!, or directly nested in a call tonotvwhich is in turn directly nested in a call toassert!, are similarly transformed.
Restricts
xto be a boolean. Ifxis equal totafter being restricted to be boolean, returnst. Ifxis equal tonilor if the value ofxis unknown returnsnil. The argumentxcan be either a variable or a non-variable.The initial restriction to boolean may cause other assertions to be made due to noticers attached to
x. A call toknown? fails ifxis known not to be boolean prior to the assertion or if any of the assertions performed by the noticers result in failure.Restricting
xto be boolean attaches a noticer onxso that any subsequent assertion which restrictsxto be non-boolean will fail.Except for the fact that one cannot write
#'known?,known? behaves like a function, even though it is implemented as a macro.The reason it is implemented as a macro is to allow a number of compile time optimizations. Expressions like
(known? (notv x)),(known? (numberpv x))and(known? (notv (numberpv x)))are transformed into calls to functions internal to Screamer which eliminate the need to create the boolean variable(s) normally returned by functions likenotvandnumberv. Calls to the functionsnumberpv,realpv,integerpv,memberv,booleanpv,=v,<v,<=v,v, >=v, /=v,notv,funcallv,applyvandequalvwhich appear directly nested in a call toknown?, or directly nested in a call tonotvwhich is in turn directly nested in a call toknown?, are similarly transformed.
Restricts
xto a be boolean. Afterxis restricted a nondeterministic choice is made. For one branch,xis restricted to equaltand(decide x)returnstas a result. For the other branch,xis restricted to equalniland(decide x)returnsnilas a result. The argumentxcan be either a variable or a non-variable.The initial restriction to boolean may cause other assertions to be made due to noticers attached to
x. A call todecideimmediately fails ifxis known not to be boolean prior to the assertion or if any of the assertions performed by the noticers result in failure.Restricting
xto be boolean attaches a noticer onxso that any subsequent assertion which restrictsxto be non-boolean will fail.Except for implementation optimizations
(decide x)is equivalent to:(EITHER (PROGN (ASSERT! X) T) (PROGN (ASSERT! (NOTV X)) NIL))Except for the fact that one cannot write
#'decide,decidebehaves like a function, even though it is implemented as a macro.The reason it is implemented as a macro is to allow a number of compile time optimizations. Expressions like
(decide (notv x)),(decide (numberpv x))and(decide (notv (numberpv x)))are transformed into calls to functions internal to Screamer which eliminate the need to create the boolean variable(s) normally returned by functions like notv and numberv. Calls to the functionsnumberpv,realpv,integerpv,memberpv,booleanpv,=v,<v,<=v,>v,>=v,/=v,notv,funcallv,applyvandequalvwhich appear directly nested in a call to decide, or directly nested in a call tonotvwhich is in turn directly nested in a call to decide, are similarly transformed.
Returns
tifxis known to be numeric,nilifxis known to be non-numeric, and otherwise returns a new boolean variablev.The values of
xandvare mutually constrained via noticers so thatvis equal totif and only ifxis known to be numeric andvis equal tonilif and only ifxis known to be non-numeric.
- If
xlater becomes known to be numeric, a noticer attached toxrestrictsvto equalt. Likewise, ifxlater becomes known to be non-numeric, a noticer attached toxrestrictsvto equalnil.- If
vever becomes known to equaltthen a noticer attached tovrestrictsxto be numeric. Likewise, ifvever becomes known to equalnilthen a noticer attached tovrestrictsxto be non-numeric.
Returns
tifxis known to be real,nilifxis known to be non-real, and otherwise returns a new boolean variablev.The values of
xandvare mutually constrained via noticers so thatvis equal totif and only ifxis known to be real andvis equal tonilif and only ifxis known to be non-real.
- If
xlater becomes known to be real, a noticer attached toxrestrictsvto equalt. Likewise, ifxlater becomes known to be non-real, a noticer attached toxrestrictsvto equalnil.- If
vever becomes known to equaltthen a noticer attached tovrestrictsxto be real. Likewise, ifvever becomes known to equalnilthen a noticer attached tovrestrictsxto be non-real.
Returns
tifxis known to be integer valued, andnilifxis known be non-integer value.If it is not known whether or not
xis integer valued whenintegerpvis called thenintegerpvcreates and returns a new boolean variablev.The values of
xandvare mutually constrained via noticers so thatvis equal totif and only ifxis known to be integer valued, andvis equal tonilif and only ifxis known to be non-integer valued.If
xlater becomes known to be integer valued, a noticer attached toxrestrictsvto equalt. Likewise, ifxlater becomes known to be non-integer valued, a noticer attached toxrestrictsvto equalnil.Furthermore, if
vever becomes known to equaltthen a noticer attached tovrestrictsxto be integer valued. Likewise, ifvever becomes known to equalnilthen a noticer attached tovrestrictsxto be non-integer valued.
Returns
tifxis known to be a member ofsequence(using the Common Lisp functioneqlas a test function),nilifxis known not to be a member ofsequence, and otherwise returns a new boolean variablev.When a new variable is created, the values of
xandvare mutually constrained via noticers so thatvis equal totif and only ifxis known to be a member ofsequenceandvis equal tonilif and only ifxis known not to be a member ofsequence.The current implementation imposes two constraints on the parameter
- If
xlater becomes known to be a member ofsequence, a noticer attached toxrestricts v to equalt. Likewise, ifxlater becomes known not to be a member ofsequence, a noticer attached toxrestrictsvto equalnil.- If
vever becomes known to equaltthen a noticer attached tovrestrictsxto be a member ofsequence. Likewise, ifvever becomes known to equalnilthen a noticer attached tovrestrictsxnot to be a member ofsequence.sequence. First,sequencemust be bound whenmembervis called. Second,sequencemust not contain any unbound variables whenmembervis called.The value of parameter
sequencemust be a sequence, i.e. either a list or a vector.
Returns
tif the aggregate objectxis known to equal the aggregate objecty,nilif the aggregate objectxis known not to equal the aggregate objecty, and a new boolean variablevif it is not known whether or notxequalsywhenequalvis called.The values of
x,yandvare mutually constraints via noticers so thatvequalstif and only ifxis known to equalyandvequalsnilif and only ifxis known not to equaly.Noticers are attached to
vas well as to all variables nested in both inxandy. When the noticers attached to variables nested inxandydetect thatxis known to equalythey restrictvto equalt. Likewise, when the noticers attached to variables nested inxandydetect thatxis known not to equalythey restrictvto equalnil.Furthermore, if
vlater becomes known to equaltthenxandyare unified. Likewise, ifvlater becomes known to equalnilthenxandyare restricted to not be equal. This is accomplished by attaching noticers to the variables nested inxandywhich detect whenxbecomes equal toyand fail.The expression
(known? (equalv x y))is analogous to the extra-logical predicate==typically available in Prolog.The expression
(known? (notv (equalv x y)))is analogous to the extra-logical predicate \= typically available in Prolog.The expression
(assert! (equalv x y))is analogous to Prolog unification.The expression
(assert! (notv (equalv x y)))is analogous to the disunification operator available in Prolog-II.
Returns a boolean value which is constrained to be
tif all of the arguments are numerically equal, and constrained to benilif two or more of the arguments numerically differ.This function takes one or more arguments. All of the arguments are restricted to be numeric.
Returns
twhen called with one argument. A call such as(=v x1 x2 ... xn)with more than two arguments behaves like a conjunction of two argument calls:(ANDV (=V X1 X2) ... (=V Xi Xi+1) ... (=V Xn-1 Xn))When called with two arguments, returns
tifx1is known to be equal tox2at the time of call,nilifx1is known not to be equal tox2at the time of call, and a new boolean variablevif is not known if the two values are equal.Two numeric values are known to be equal only when they are both bound and equal according to the Common Lisp function
=.Two numeric values are known not to be equal when their domains are disjoint. Furthermore, two real values are known not to be equal when their ranges are disjoint, i.e. the upper bound of one is greater than the lower bound of the other.
When a new variable is created, the values of
x1,x2, andvare mutually constrained via noticers so thatvis equal totif and only ifx1is known to be equal tox2, andvis equal tonilif and only ifx1is known not to be equal tox2.Restricting two values x1 and x2 to be equal is performed by attaching noticers to x1 and x2. These noticers continually restrict the domains of x1 and x2 to be equivalent sets (using the Common Lisp function
- If it later becomes known that
x1is equal tox2noticers attached tox1andx2restrictvto equalt. Likewise if it later becomes known thatx1is not equal tox2noticers attached tox1andx2restrictvto equalnil.- If
vever becomes known to equaltthen a noticer attached tovrestrictsx1to be equal tox2. Likewise ifvever becomes known to equalnilthen a noticer attached tovrestrictsx1not to be equal tox2.- If
x1is known to be real then the noticer attached tox2continually restrict the upper bound ofx1to be no higher than the upper bound ofx2and the lower bound ofx1to be no lower than the lower bound ofx2. Likewise for bounds ofx1ifx2is known to be real.=as a test function) as their domains are restricted.Restricting two values
x1andx2to not be equal is also performed by attaching noticers tox1andx2. These noticers however do not restrict the domains or ranges ofx1orx2. They simply monitor their continually restrictions and fail when any assertion causesx1to be known to be equal tox2.
Returns a boolean value which is constrained to be
tif no two arguments are numerically equal, and constrained to benilif any two or more arguments are numerically equal.This function takes one or more arguments. All of the arguments are restricted to be numeric.
Returns
twhen called with one argument. A call such as(/=v x1 x2 ... xn)with more than two arguments behaves like a conjunction of two argument calls:(ANDV (/=V X1 X2) ... (/=V X1 Xn) (/=V X2 X3) ... (/=V X2 Xn) ... (/=V Xi Xi+1 ... (/=V Xi Xn) ... (/=V Xn-1 xn))When called with two arguments, returns
tifx1is known not to be equal tox2at the time of call,nilifx1is known to be equal tox2at the time of call, and otherwise a new boolean variablev.Two numeric values are known not to be equal when their domains are disjoint.
Two real values are known not to be equal when their ranges are disjoint, i.e. the upper bound of one is greater than the lower bound of the other.
Two numeric values are known to be equal only when they are both bound and equal according to the Common Lisp function
=.When a new variable is created, the values of
x1,x2andvare mutually constrained via noticers so thatvis equal totif and only ifx1is known not to be equal tox2andvis equal tonilif and only ifx1is known to be equal tox2.Restricting two values
- If it later becomes known that
x1is not equal tox2, noticers attached tox1andx2restrictvto equalt. Likewise, if it later becomes known thatx1is equal tox2, noticers attached tox1andx2restrictvto equalnil.- If
vever becomes known to equaltthen a noticer attached tovrestrictsx1to not be equal tox2. Likewise, ifvever becomes known to equalnilthen a noticer attached tovrestrictsx1to be equal tox2.x1andx2to be equal is performed by attaching noticers tox1andx2. These noticers continually restrict the domains ofx1andx2to be equivalent sets (using the Common Lisp function=as a test function) as their domains are restricted. Furthermore, ifx1is known to be real then the noticer attached tox2continually restrict the upper bound ofx1to be no higher than the upper bound ofx2and the lower bound ofx1to be no lower than the lower bound ofx2. The noticer ofx2performs a symmetric restriction on the bounds ofx1if it is known to be real.Restricting two values
x1andx2to not be equal is also performed by attaching noticers tox1andx2. These noticers however, do not restrict the domains or ranges ofx1orx2. They simply monitor their continually restrictions and fail when any assertion causesx1to be known to be equal tox2.
Returns a boolean value which is constrained to be
tif each argument Xi is less than the following argument Xi+1 and constrained to benilif some argument Xi is greater than or equal to the following argument Xi+1.This function takes one or more arguments. All of the arguments are restricted to be real.
Returns
twhen called with one argument. A call such as(<v x1 x2 ... xn)with more than two arguments behaves like a conjunction of two argument calls:(ANDV (<V X1 X2) ... (<V Xi Xi+1 ) ... (<V XNn-1 Xn))When called with two arguments, returns
tifx1is known to be less thanx2at the time of call,nilifx1is known to be greater than or equal tox2at the time of call, and otherwise a new boolean variablev.A real value
x1is known to be less than a real valuex2ifx1has an upper bound,x2has a lower bound and the upper bound ofx1is less than the lower bound ofx2.A real value
x1is known to be greater than or equal to a real valuex2ifx1has a lower bound,x2has an upper bound and the lower bound ofx1is greater than or equal to the upper bound ofx2.When a new variable is created, the values of
x1,x2and v are mutually constrained via noticers so thatvis equal totif and only ifx1is known to be less thanx2andvis equal tonilif and only ifx1is known to be greater than or equal tox2.Restricting a real value
- If it later becomes known that
x1is less thanx2, noticers attached tox1andx2restrictvto equalt. Likewise, if it later becomes known thatx1is greater than or equal tox2, noticers attached tox1andx2restrictvto equalnil.- If
vever becomes known to equaltthen a noticer attached tovrestrictsx1to be less thanx2. Likewise, ifvever becomes known to equalnilthen a noticer attached tovrestrictsx1to be greater than or equal tox2.x1to be less than a real valuex2is performed by attaching noticers tox1andx2. The noticer attached tox1continually restricts the lower bound ofx2to be no lower than the upper bound ofx1ifx1has an upper bound. The noticer attached tox2continually restricts the upper bound ofx1to be no higher than the lower bound ofx2ifx2has a lower bound. Since these restrictions only guarantee thatx1be less than or equal tox2, the constraint thatx1be strictly less thanx2is enforced by having the noticers fail when bothx1andx2become known to be equal.Restricting a real value
x1to be greater than or equal to a real valuex2is performed by an analogous set of noticers without this last equality check.
Returns a real variable whose value is constrained to be greater than or equal to
low.
Returns a real variable whose value is constrained to be less than or equal to
high.
Returns a real variable whose value is constrained to be greater than or equal to low and less than or equal to high. If the resulting real variable is bound, its value is returned instead. Fails if it is known that low is greater than high at the time of call.
The expression
(a-real-betweenv low high)is an abbreviation for:(LET ((V (MAKE-VARIABLE))) (ASSERT! (REALPV V)) (ASSERT! (>=V V LOW)) (ASSERT! (<=V V HIGH)) (VALUE-OF V))
Returns an integer variable whose value is constrained to be greater than or equal to
low.
Returns an integer variable whose value is constrained to be less than or equal to
high.
Returns an integer variable whose value is constrained to be greater than or equal to
lowand less than or equal tohigh. If the resulting integer variable is bound, its value is returned instead. Fails if it is known that there is no integer betweenlowandhighat the time of call.The expression
(an-integer-betweenv low high)is an abbreviation for:(LET ((V (MAKE-VARIABLE))) (ASSERT! (INTEGERPV V)) (ASSERT! (>=V V LOW)) (ASSERT! (<=V V HIGH)) (VALUE-OF v))
Discretize integer variables whose range is not greater than this number. Discretize all integer variables if
nil. Must be an integer ornil.
Ignore propagations which reduce the range of a variable by less than this ratio.
Strategy to use for
funcallvandapplyv. Either:gfcfor Generalized Forward Checking, or:acfor Arc Consistency. Default is:gfc.
Removes any information about
function-namefrom Screamer's who-calls database.
Removes any information about all user defined functions from Screamer's who-calls database.
Set to
tto enable the dynamic extent optimization,nilto disable it. Default is platform dependent.