Searched refs:other (Results 76 - 100 of 230) sorted by relevance

12345678910

/barrelfish-master/usr/eclipseclp/documents/tutorial/
H A Dmodelling.tex92 On the other hand, it is not necessarily easy to see how they can be
122 There are many other approaches to problem modelling software.
408 are just rotated and mirrored variants of each other.
/barrelfish-master/doc/021-cpudriver/
H A Dcpudriver.tex166 access flags. All other flags are not settable from user-space (like
271 point of the dispatcher. All other exceptions are dispatched to the
350 common with other architectures.
/barrelfish-master/usr/eclipseclp/documents/applications/
H A Dtutorial.tex74 techniques, which can be found in other tutorials. This current report
100 The methodology developed in the CHIC-II project \index{CHIC-II} looks at a much wider methodology question (http://www.icparc.ic.ac.uk/chic2/methodology/)\index{methodology}. It not only covers problems like how to select a problem solving technology to fit a particular problem, but also discusses project related issues like team composition\index{team composition}, rapid prototyping\index{rapid prototyping} and development of problem specifications. On the other hand, it does not discuss the details of developing an ECLiPSe application once the main design choices have been taken.
102 The book ``The Craft of Prolog'' by Richard O'Keefe is an invaluable source for writing efficient Prolog programs. Many of the techniques and tricks presented are also applicable to writing efficient ECLiPSe programs. The underlying maxim ``elegance is not optional'' summarizes the spirit of declarative programming. As the book is based on a standard Edinburgh style Prolog, it does not handle issues of module structure and in-line documentation, nor other ECLiPSe specific features.
104 The ECLiPSe documentation contains most of the information provided in this tutorial, but presents it in a very different way. Invariably, it describes all features of the system, many of which are only required for quite specific (if important) tasks like developing new constraint engines inside the system. It can be difficult to find which parts of the documentation contains important hints to solve a particular problem. On the other hand, it will be useful to look up each feature in the user manual and/or the reference manual as they occur in the tutorial.
120 We first review the overall application structure\index{application structure} found in systems developed at Parc Technologies (at least those using ECLiPSe for part of their development). We distinguish between two application types, one a full application with user-interface, database, reporting, etc, and the other a much smaller system, typically reading data from and to files and performing a single, batch type operation.
164 Examples of the first type (see figure~\ref{fullapplication}) are Parc Technologies applications (http://www.parc-technologies.com) like AirPlanner\index{AirPlanner} and RiskWise\index{RiskWise}\footnote{In the following we use a number of examples from the RiskWise application. It is a network analysis tool for IP networks, which uses a constraint solver to determine traffic pattern in the network. If this doesn't make any sense to you, relax. An understanding of the networking application domain is not required to follow this tutorial.}, where everything except the problem solver is developed in Java\index{Java} or related tools. The interface between the main application and the problem solver written in ECLiPSe is via a Java-ECLiPSe interface. In this interface, the main application poses queries for the ECLiPSe solver, passing data and arguments into ECLiPSe. The problem solver then runs the query and returns results as variable bindings in the given query. The Java side only knows about these queries, their data format and the expected results. The internals of the solver, how the queries are resolved, is completely hidden. This defines a nice interface between the application parts, as long as the queries are well defined and documented. Once that design is frozen, the developers for the different parts can continue development independently from each other, using stubs or dummy routines to simulate the other application parts.
208 Once the external API is clearly defined, we can start looking at the next level of internal structure. This will depend on the intended purpose of the system, but we can identify some typical structures that can be found in many applications. Here, we present two typical designs, one for solving combinatorial problems, the other for transforming data.
266 The main limitation of this approach is that all data must be loaded into the application (in main memory)\index{main memory}. This limits the size of the data sets that can be handled to several megabytes. On the other hand, all information can be made available in an efficient way using lookup hash tables or arrays, so that the implementation of the transformation is quite simple.
269 Once we have decided on a top-level structure, we must consider the input/output arguments of each part. We have to decide which data must be fed into which modules, where new data structures will be created and which other module
[all...]
/barrelfish-master/usr/eclipseclp/documents/libman/
H A Dgfd.tex115 constraints, and specify the domain for variables before using them in other
170 posting a constraint at the other three consistency levels is supported only
236 GFD's constraints (and other predicates) follows several conventions
613 for the other relations:
678 Constraints for the other lexicographic relations:
881 Constraints that don't fit into the other categories.
924 {\eclipse} level, and/or if you are using other solvers during the search.
926 On the other hand, GFD's search/6 is less flexible than the generic search
950 strategies on the other hand always interleave value choices with variable
998 As soon as any user-defined constraints or any other {\eclips
[all...]
H A Dmp.tex149 \item [...] There may be other events that need to notify the application.
167 The other way is to build on top of the PDS library (\cite{kees},
/barrelfish-master/usr/eclipseclp/documents/megalog/
H A Dmanual.tex115 a single built-in but a concept that is used in other descriptions.
H A Dmultiuser-sec.tex57 exclusively, preventing other users from using it at the same time.
95 per user and invisible to other users. Access to both types of relation
177 has a write lock no other can have any lock on it at the
261 is not possible for other reasons.
H A Ddatabase-sec.tex137 can be open at a time). To close a database in other circumstances the
186 is unique (i.e. no other relation shares this name) and of no more
216 less efficient and should not be used where one of the three other types
409 to determine which tuples from other relations should be inserted into it.
549 with each other or with constants using any comparison operator.
583 with each other or with constants using any comparison operator.
938 On the other hand the tuple access allows an easy interference with
984 Backtracking can then be invoked to delete other tuples from the database
/barrelfish-master/usr/eclipseclp/documents/userman/
H A Dumssocket.tex53 all other streams, and so it is necessary to flush
92 The other process uses the same name when connecting to
156 Any other process can then connect directly to this socket
168 the other direction
H A Dextmeta.tex49 it can be unified with other terms and
148 \about{Attr} and all its other attributes are free variables.
289 the attributed variable is bound (like a standard variable) to the other term
342 uninstantiated attribute) variable with any other term.
542 should not decide whether the other attributes will be printed or not.
553 For other type testing predicates an attributed variable behaves like a
H A Dumsmodules.tex71 and optionally in other modules when they are made available.
110 into all other modules.
179 And the same holds for operators and other syntax settings:
197 Unlike the other declarations above, an exported
506 matches the module name, and the other files should be referenced
709 in particular information about the module's interface, what other
H A Dexthsusp.tex201 Note that more powerful versions of these constraints exist in other
629 If this happens, we check whether other variables remain, and if yes,
666 unified with each other (aliased).
705 there are other ways. The most obvious example are variable domains:
867 Of course, symbolic triggers can be used together with other
891 \item it might not have any other waking conditions left;
892 \item and it might at the same time have other waking conditions left
1264 Or, in other words, the demon goal forks into one goal that remains in the
1387 and which do not do any bindings or other updates.
1392 propagate changes to other variable
[all...]
/barrelfish-master/lib/openssl-1.0.0d/crypto/conf/
H A Dkeysets.pl84 * documentation and/or other materials provided with the distribution.
/barrelfish-master/lib/openssl-1.0.0d/crypto/ts/
H A Dts_asn1.c16 * the documentation and/or other materials provided with the
310 tst_info_wrapper = enveloped->d.other;
/barrelfish-master/usr/eclipseclp/Contrib/
H A Dcardinal_comments.pl29 % and other provisions required by the GPL or the LGPL. If you do not delete
37 on sets cardinality and other optional set functions (minimum and maximum for
75 other than Cardinal do not make such inferences.
101 bound (glb) or meet of P(U), since there is no other upper bound contained in
102 (�less� than) U nor other lower bound containing (�greater� than) the empty set {}.
110 by its interval (lattice); all other sets outside this domain are excluded from
112 other possible elements.
142 (other than cardinality): minimum and maximum, for sets of integers, and union,
H A Dcardinal_functions.pl30 % and other provisions required by the GPL or the LGPL. If you do not delete
H A Doccur.pl74 % It may be at other places too, so the predicate is prepared to
H A Drdtok.pl31 other where.
202 % it can ever fail. The other complication is that when we find a Quote
279 % reads the other kind of atom which needs no quoting: one which is
/barrelfish-master/doc/015-disk-driver-arch/
H A Dfuture.tex51 backends for other controllers. Since this lab project only examined
H A Dflounder-ahci.tex20 must be formatted in a particular way, other actions may be necessary, and
70 Among other things, this requires an additional step between parsing
/barrelfish-master/tools/harness/tests/
H A Dwebserver.py352 ' ftab-full (\d+) other (\d+)', line)
422 def __add__(self, other):
425 setattr(ret, f, getattr(self, f) + getattr(other, f))
/barrelfish-master/doc/011-idc/
H A DIDC.tex110 separators, terminators or for other special purposes in Flounder:
345 All other options cause Flounder to emit the C code generated by one of its
347 code that is shared by all other backends, and is always required.
390 In any binding attempt, one dispatcher must act as server and the other as
712 other dispatchers. Although there is no limit to the number of waitsets used,
727 into the state of a real message channel or other event mechanism.
823 \item Otherwise, if there are any channels in the polled queue, and no other
856 kernel-mediated communication with other dispatchers on the same core,
921 The binding mechanisms for other interconnect drivers (e.g. LMP, BMP) are
932 For other interconnec
[all...]
/barrelfish-master/usr/eclipseclp/documents/embedding/
H A Dembvb.tex33 interfaces for other languages.
77 Initialise the {\eclipse} engine. This is required before any other
/barrelfish-master/doc/016-serial-ports/
H A DSerial.tex57 drivers and other console subsystems.
183 functionality in \Intf that deals with physical serial ports, in other
/barrelfish-master/lib/openssl-1.0.0d/crypto/pkcs7/
H A Dpk7_doit.c30 * documentation and/or other materials provided with the distribution.
99 if ( PKCS7_type_is_other(p7) && p7->d.other
100 && (p7->d.other->type == V_ASN1_OCTET_STRING))
101 return p7->d.other->value.octet_string;

Completed in 594 milliseconds

12345678910