| /barrelfish-master/usr/eclipseclp/documents/libman/ |
| H A D | repair.tex | 202 \index{conflict constraint}
203 {\em conflict constraint}.
217 When the constraint goes into conflict, it will show up in the
218 conflict set denoted by {\bf ConflictSet}, from where it can be
224 a variable in which case the system returns a conflict set handle that can
230 Note that using different conflict sets for different groups of constraints
236 If this is used, {\bf ConflictData} will appear in the conflict
250 conflict for the first time. If {\bf Constraint} is a finite-domain
272 conflict sets.
273 Typically, a search algorithm examines the conflict se
[all...] |
| /barrelfish-master/lib/openssl-1.0.0d/crypto/engine/ |
| H A D | eng_list.c | 98 int conflict = 0; local
108 while(iterator && !conflict)
110 conflict = (strcmp(iterator->id, e->id) == 0);
113 if(conflict)
|
| /barrelfish-master/usr/eclipseclp/documents/tutorial/ |
| H A D | repairtut.tex | 54 Finally there are techniques such as conflict minimisation which seek
108 \index{conflict sets}
119 This query also succeeds - but additionally it creates a {\em conflict
122 $X$, the constraint is recorded in the conflict set. The conflict set
132 The conflict can be {\em repaired} by changing the tentative value of
179 \index{conflict\_constraints/2}
194 \index{conflict minimisation}
202 Finding a constraint in conflict, and labelling a variable in this
206 there are no more constraints in conflict
[all...] |
| H A D | setsolver.tex | 198 the {\em ic_sets} module prefix because of a name conflict with a predicate from
|
| /barrelfish-master/lib/openssl-1.0.0d/VMS/ |
| H A D | openssl_utils.com | 20 $! REQ could conflict with REQUEST.
|
| /barrelfish-master/usr/eclipseclp/icparc_solvers/ |
| H A D | repair.pl | 34 % see constraints that are in conflict just because the tentative
37 % Later, we may want to consider these constraints as being in conflict
107 % conflict_constraints = suspensions of repair constraints in conflict
115 :- local struct(monitor_conflict(constraint,annotation,conflict,prop,module)).
116 :- local struct(tent_is_conflict(expr,annotation,sum,outsum,conflict,susp,module)).
275 % The conflict vars set is those variables that are untenable. All of these
278 % The conflict constraints set contains constraints that are untenable.
280 % constraint into the conflict vars set.
284 % that its delayed goals list is exactly the conflict constraint set.
331 % like r_conflict but calls Goal when it goes into conflict
619 conflict:ConfElem, label
648 conflict:ConfElem,prop:PropFlag,module:Module} :- label
[all...] |
| /barrelfish-master/usr/eclipseclp/Opium/demo/ |
| H A D | collect.pl | 37 diff_member(X,[Y|T]-T) :- % conflict with Opium member/2
|
| /barrelfish-master/usr/eclipseclp/documents/userman/ |
| H A D | umsmodules.tex | 299 \index{name conflict}
302 \item[Import/Import conflict:]
305 \item[Import/Local conflict:]
311 long as there is no reference to the conflict predicate. Only when an attempt
313 is made to access the conflict predicate is an error raised.
314 The conflict can be resolved by explicitly importing one of the versions, e.g.,
319 :- import (#>=)/2 from ria. % resolves the conflict
322 Alternatively, the conflict can remain unresolved and qualified access can
401 import the predicate because of the name conflict with the local
|
| H A D | umscmdlineopts.tex | 109 This can be an arbitrary name, as long as it does not conflict with
|
| H A D | umsporting.tex | 116 conflict with ISO. As some of these extensions go beyond what the
|
| H A D | umscompiler.tex | 630 naming conflict can occur and the old auxiliaries may be replaced. It is
|
| /barrelfish-master/lib/lua/src/ |
| H A D | lparser.c | 1111 int conflict = 0; local
1116 conflict = 1;
1122 conflict = 1;
1127 if (conflict) {
|
| /barrelfish-master/usr/eclipseclp/documents/search/ |
| H A D | search.tex | 1082 specified {\em conflict set}.
1084 {\bf r\_conflict} and it will appear in the conflict set called
1149 the automatic recomputation of the conflict constraint set
1157 is checked by looking at the conflict constraints. If there are no
1158 conflict constraints, the constraints are all tentatively satisfied
1264 by checking whether the conflict constraint set is empty.
1417 The min-conflict heuristic of Minton et al. is the heuristic used to
1422 causes the minimum conflict (constraint violation) with the tentative
1659 tentative values are causing conflict. The repair library maintains the
1660 (repair) constraints which are causing conflict, an
[all...] |
| /barrelfish-master/usr/eclipseclp/Kernel/lib/ |
| H A D | fd_elipsys.pl | 62 % These seem broken, and also conflict with the global_gac versions
|
| H A D | io.pl | 321 % In case of conflict, use the rightmost option
|
| /barrelfish-master/usr/eclipseclp/Usc/src/ |
| H A D | configure | 668 which can conflict with char $ac_func(); below. */
|
| /barrelfish-master/usr/eclipseclp/documents/internal/kernel/ |
| H A D | io.tex | 142 notably "not/foo" because of the conflict between low-precedence
|
| /barrelfish-master/usr/eclipseclp/documents/intro_paper/ |
| H A D | eclipse.tex | 2371 Such conflict sets can be used to impose extra constraints called {\em
2415 detecting a variable whose tentative value is in conflict with a
2445 conflict constraint}, and full propagation on the constraint is
2447 The set of conflict constraints can be accessed via the predicate {\em
2448 conflict\_constraints}.
2496 This approach requires no backtracking, since every conflict can be
2504 Variables in conflict are repaired - by instantiating them - until
2507 The latter situation occurs when some variable in conflict cannot
|
| /barrelfish-master/usr/eclipseclp/Shm/src/ |
| H A D | configure | 5479 which can conflict with char $ac_func (); below.
|
| /barrelfish-master/usr/eclipseclp/ |
| H A D | configure | 2129 which can conflict with char $2 (); below.
|