/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/ |
H A D | extsuspend.tex | 249 success, failure and delay. 283 necessary to detect failure -- the two terms can become 438 It uses the approach of ``eager failure'' and ``lazy success''.
|
H A D | umsarrays.tex | 72 information across failure, but provides a means to give a name to 317 failure-driven loop to provide
|
H A D | umsdebug.tex | 104 The flow of the execution from the failure of one clause to the 763 \cmd{q}{query the failure culprit}\\ 766 number of the goal which caused the failure. You can then re-run the 775 failure culprit was (3) - rerun and type q to jump there %> nodebug? [y] 780 failure culprit was (3) - jump to invoc: [3]? 921 Force a failure of the procedure with the specified invocation number. 922 The default is to force failure of the current procedure.
|
H A D | umscompiler.tex | 327 solution. No results are printed by the system, failure leads to a warning, 833 Usually, an unexpected failure occurs in this case. 955 If the space is known to be deallocated anyway, e.g., on failure,
|
H A D | umsintro.tex | 279 %%In addition to the usual {\it negation by failure},
|
H A D | umsterm.tex | 145 yes | failure semidet nondet
|
H A D | umsexcept.tex | 68 % \item failure of the handler is ignored. 310 asynchronous events should never fail, because the failure will be inserted
|
H A D | umsio.tex | 337 by handle are closed automatically, either on failure across the 340 be taken to ensure that streams are closed on failure or when
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/search/ |
H A D | search.tex | 607 causes immediate failure due to constraint propagation) is not counted. 1517 simple failure will cause the procedure to fail back to the beginning, 1550 nogood must be done {\it after\/} the failure and backtracking from the 1554 the point just before the failure, which can then be retrieved after the 1555 failure to produce a new nogood constraint. Not only do the values 1583 \verb'remember_nogood/1' is called before the actual failure is allow to occur: 1709 failure if this is the case. If a non-matching variable-value pair is
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/internal/kernel/ |
H A D | kernel.tex | 576 As a result, failure can occur. In case of success, the MU\index{MU} register may 917 failure & goto failure continuation \\ 939 set_bp(ref(L)) & save failure continuation (push small choicepoint) \\ 940 restore_bp & restore failure continuation (pop small choicepoint) \\ 941 new_bp(ref(L)) & update failure continuation (modify small choicepoint) \\ 1305 to trace this event even if the failure continuation is within code 1439 the undo function will only be called on failure. 1460 on failure (unless redundant according to stamp), or in 1491 during failure [all...] |
H A D | umscmacros.tex | 75 {\tt Fail_} & return from procedure as a failure.\\ 601 % call the goal in the module, but report only success or failure.
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/ |
H A D | embed.tex | 245 success and failure continuations and its global stack of all 295 or whether a failure occurred. 322 \index{failure}
|
H A D | umscmacros.tex | 63 {\tt Fail} & return from procedure as a failure.\\ 591 call the goal in the module, but report only success or failure.
|
/barrelfish-2018-10-04/usr/eclipseclp/ |
H A D | BUILD_ROTD | 531 # Usage: remote_commands <machine> <directory> <commands> [<failure count>] 895 # failure). 954 || true # Ignore failure if no if_*.tgz files exist. 960 # Ignore cp failure if no if_*.tgz files exist 988 # looks like a failure. 1458 echo "Testing machine $1 (phase $2) completed: failure."
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/libman/ |
H A D | gfd.tex | 1011 other {\eclipse} solvers, like accumulated failure count.
1089 \eclipse's solvers, such as weighted degree (a.k.a. accumulated failure count).
1107 propagation failure.
1377 Returns the weighted degree (wdeg, accumulated failure count) of domain
1407 When failure occurs, Gecode does not backtrack to a previous computation
|
H A D | eplex.tex | 219 current bounds, and failure will occur if the resulting interval is empty. 977 \item if the problem is infeasible, then failure occurs as normal (with the 1081 the bounds of the columns are merged (and failure will occur if the
|
H A D | extfd.tex | 238 found solution, failure is forced and a new solution is searched for. 250 from the beginning, but a failure is forced and the search continues. 844 is usually quickly reduced and either an early failure occurs
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/applications/ |
H A D | tutorial.tex | 1722 \section{Understanding failure} 1723 We can distinguish five types of failure\index{failure}, each with its own set of causes and possible remedies. 1776 \subsection{Failure} Probably the most common error symptom is a failure\index{failure} of the application. Instead of producing an answer, the system returns 'no'\index{no}. This is caused by: 1778 \item Calling a user-defined predicate \index{user defined predicate}with the wrong calling pattern. If none of the rules of a predicate matches the calling pattern, then the predicate will fail. Of course, quite often this is intentional (tests for some condition for example). It becomes a problem if the calling predicate does not handle the failure properly. We should know for each predicate that we define if it can fail and make sure that any calling predicate handles that situation. 1782 The best way of finding failures is by code inspection, helped by logging messages which indicate the general area of the failure. If this turns out to be too complex, we may have to use the tracer. 1832 or which can be directed to a log file. This can be useful in ``live'' code, in order to capture information about problems in failure cases. 1948 \item The final code should not use failure-loops\index{failure loo [all...] |
/barrelfish-2018-10-04/doc/011-idc/ |
H A D | IDC.tex | 416 error code indicating success or failure of the export, and an \emph{interface 428 binding process will complete. If it returns an error code indicating failure, 454 \lstinline+iface_bind()+, an error code indicating success or failure, and a
|
/barrelfish-2018-10-04/usr/eclipseclp/Contrib/ |
H A D | cardinal_comments.pl | 83 inferred that #Z =< 2). A failure could thus be immediately detected upon the 627 and exclusion of the first element of its poss leads to a failure due to 738 propagation leads to a failure).",
|
H A D | distfix.pl | 43 distfixop(1105, fx, [try,Goal,reverting,to,Alternative,on,failure],
|
/barrelfish-2018-10-04/usr/eclipseclp/Opium/demo/ |
H A D | yoyo3.pl | 32 BUGGY: endless loop (failure-driven). \n').
|
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/ |
H A D | io.pl | 1005 % events are deferred again even on failure/throw. 1747 /* ensure that multitask phase is ended properly: if failure or 1797 % ignore failure (invalid terms substituted by _)
|
H A D | megalog.pl | 252 error and failure if array exists with different boundaries
|
H A D | tracer_tty.pl | 331 printf(debug_output, "failure culprit was (%d) - ", [CulpritInvoc]), 339 "failure culprit was (%d) - the goal you are currently at", 343 "failure culprit was (%d) - rerun and type q to jump there", 349 write(debug_output, "no failure culprit stored yet"), 572 q jump to the most recent failure's culprit\n\
|