Searched refs:part (Results 1 - 25 of 115) sorted by relevance

12345

/barrelfish-2018-10-04/doc/015-disk-driver-arch/
H A Ddesign.tex43 main parts: a management part and a communication part. The management part,
45 The communication part, consisting of libahci (a low-level abstraction for
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/
H A Darray.pl34 * IDENTIFICATION: array.pl, part of module(sepia_kernel)
H A Dtconv.pl32 * IDENTIFICATION: tconv.pl, part of module(sepia_kernel)
H A Dpdb.pl34 * IDENTIFICATION: pdb.pl, part of module(sepia_kernel)
H A Dqueues.pl170 unifies Head with the first element of the queue. The tricky part
H A Dt_all.pl36 % need to provoke error messages as part of the test
/barrelfish-2018-10-04/usr/skb/programs/
H A Dthreadallocation.pl37 % create a list of threads so that every one works on one part of a bigger address
/barrelfish-2018-10-04/usr/eclipseclp/documents/megalog/
H A Dintro-sec.tex43 i.e.\ the MegaLog part. A description of the Prolog functionality
44 -- i.e. the Sepia part -- is found in \cite{SP91}.
156 between \eclipse and the Prolog part of MegaLog are hidden.
H A Dbackwards-sec.tex36 MegaLog system with a Prolog part independent of \eclipse. This
/barrelfish-2018-10-04/usr/eclipseclp/documents/internal/kernel/
H A Dgc.tex35 This choicepoint virtually separates all stacks into an old and a new part,
36 The part of the global stack newer than this choicepoint
146 The chain pointer of course overwrites at least a part of the original
150 can now be used to preserve the overwritten part of the target object.
H A Dbuiltins.tex73 code sequences that are part of the runtime system. Files:
180 an number of option flags are part of a syntax descriptor that is stored
H A Dkernel.tex133 value val; /* value part first */
134 type tag; /* then tag part */
170 value part of the pword contains a pointer to a buffer, which in turn
184 Atoms\index{Atoms} are represented with a TDICT\index{TDICT} tag, the value part being a
187 an undefined value part. The reason to have the TNIL tag is to speed
194 a TDBL tag, and the value part consisting of the actual double value.
195 On 32-bit machines, doubles are {\it boxed}, i.e. the value part contains
229 string is part of the dictionary (see \ref{chapdictionary}).
292 References are distinguished from free variables\index{variables} only by their value part:
550 V & value & value part o
[all...]
/barrelfish-2018-10-04/lib/openssl-1.0.0d/crypto/asn1/
H A Dasn_mime.c316 /* Now write out the first part */
611 char state, part, first; local
614 part = 0;
623 part++;
627 } else if(part) {
909 * 1 : part boundary
918 /* Check for part boundary */
/barrelfish-2018-10-04/kernel/include/
H A Dmultiboot2.h229 multiboot_uint32_t part; member in struct:multiboot_tag_bootdev
/barrelfish-2018-10-04/usr/eclipseclp/Contrib/
H A Dxml.pl83 * more flexible than output parsing. Errors in input are recorded as part
/barrelfish-2018-10-04/lib/vfs/
H A Dvfs_fat.c561 char part[part_len+1]; local
562 strncpy(part, part_begin, part_len);
563 part[part_len]=0;
564 FAT_DEBUG_F("part \"%s\"", part);
623 FAT_DEBUG_F("comparing part to %s", buf);
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/
H A Dumsmodules.tex104 The module system is flat, i.e., no module is part of another module,
107 \item a few basic modules that are part of the {\eclipse}
114 and same as the base part of the library file name.
140 suffix/extension part). For example, the module \notation{mymodule} might be
247 It is also possible to import only a part of another module's
490 When a source file contains no module directives, it becomes part of
/barrelfish-2018-10-04/doc/008-tracing/
H A DTracing.tex93 In this section we want to look at the part of the tracing framework that is
95 order to create trace logs. One part of the tracing framework allows developers
97 is defined in the Section \ref{sec:trace-event}. The second part is responsible
243 Parsing and interpreting of pleco files is part of the Barrelfish build process,
436 there are no messages exchanged as part of a protocol -- Bfscope simply sends
623 Aquarium. The largest part of the GUI is used by the so called \emph{GraphView},
644 On the left part of the GUI we see the Filter menu. It allows to filter out
683 part of the trace log data, that is interesting to you.
703 part of the source code
813 analyzing this part o
[all...]
/barrelfish-2018-10-04/usr/eclipseclp/documents/applications/
H A Dtutorial.tex120 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.
169 For each required function of the interface, we should define a specific query\index{query}. The query consists of three parts. The first is the predicate name, which obviously should have a relation to the intended function. The second part consists of the input arguments\index{input arguments}, which are used to pass information from the outside to the problem solver. The structure of these arguments should be as simple as possible, easy to generate and to analyze. The third part consists of the output arguments\index{output arguments}, which are used to pass information from the problem solver back to the calling interface. When calling the query these arguments will be free variables, which are instantiated inside the solver to some result data structure.
176 An important part of the API definition is the identification of constraints\index{constraints} attached to the data. Constraints in this context are conditions that the data must satisfy in order to obtain meaningful results. These constraints ensure that the data set is complete, minimal and consistent.
211 This structure is typical for large scale combinatorial optimization\index{large scale combinatorial optimization} (LSCO)\index{LSCO} problems. The flow analysis part of RiskWise follows this structure. It consists of five parts, where each performs one particular task.
241 Exceptions to this rule are auxiliary variables which are only introduced to express some constraint and which are not part of the problem variables proper, or constraints that are introduced inside the search process in order to find a solution.
263 \item[transform] We then use these data structures to create new, transformed data in the tranformation part of the application.
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 modules require this data. For each piece of information we must identify its source and its possible sinks. Designing these data flows is an iterative process, assigning functionality to modules and making sure that the required information is available. The design aim should be to minimize the amount of information that must be passed across module boundaries and to arrange functions in the correct data flow order, so that all information is produced before it is required in another module.
436 \item[facts] The last alternative is to store the data as facts \index{fact}in the application. They can then be accessed from any part of the ECLiPSe code quite easily. Testing the code is simple by compiling some data files into the system. The Java interface can also store facts into the database quite easily. But changing the data for a new query can be rather complex, and may require recompiling some data modules.
475 In order to use a structure, it must be defined with a {\it struct}\index{struct} definition. We can define a structure either {\it local}\index{local struct} to a module or {\it export} \index{export struct}the definition so that the same structure can be used in other modules which import the definition. As part o
[all...]
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/
H A Dembsumc.tex322 This function is part of the simplified interface.
327 This function is part of the simplified interface.
345 This function is part of the simplified interface.
371 This function is part of the simplified interface.
427 This function is part of the simplified interface.
/barrelfish-2018-10-04/doc/018-Practical-guide/
H A DhelloWorldApp.tex149 The important part of the above is in the dispatch loop where application
233 printing out the string we received as part of the message.
279 The \texttt{hello\_bind} is part of the code generated from the interface
/barrelfish-2018-10-04/usr/eclipseclp/Opium/
H A Dopium.pl41 * not part of an Opium scenario
H A Dopium_light.pl201 Patch for opium_light (overwrites part of translate.op).
/barrelfish-2018-10-04/lib/openssl-1.0.0d/
H A Dmakevms.com26 $! CRYPTO/x Just build the x part of the
308 $! algos part.
892 $! Check if there's a "part", and separate it out
/barrelfish-2018-10-04/lib/lwip2/src/
H A DFilelists.mk27 # This file is part of the lwIP TCP/IP stack.

Completed in 165 milliseconds

12345