/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/ |
H A D | exthsusp.tex | 53 % Lower-level primitives 72 top-level goal 220 As seen in the above example, the \index{top level loop} top level loop 299 is to avoid a possible mixing of meta-level control with the 300 object level, similarly to \cite{dincbas84}. 406 \predspec{suspend/3} is itself based on the lower-level primitives 907 \section{Lower-level Primitives} 1073 and to detect floundering of the query given to the {\eclipse} top-level loop. 1147 the following low-level primitive [all...] |
H A D | extmeta.tex | 38 for an object-level program, a metaterm looks like a variable, but for 40 together with additional meta-level information, forms the metaterm. 213 which is ignored by ordinary \emph{object level} system predicates. 214 \emph{Meta level} operations on attributed variables are handled by
|
H A D | umssocket.tex | 147 at the system level, however at the Prolog level the packet
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/applications/ |
H A D | tutorial.tex | 86 This tutorial is an introduction to the design, development, test and maintenance of large scale applications with the ECLiPSe system. It follows a top-down methodology of converting an initial high-level specification into executable code of high quality. We assume that fundamental decisions on selecting the right tool and the right problem solver have already been taken so that we are commited to using ECLiPSe and one of its problem solving libraries. We are basically interested in the engineering aspects of the program development, not its research and development content. 109 The tutorial follows a top-down methodology for the design of an application. Chapter~\ref{highleveldesign} discusses general issues of modular design and self-documenting code for ECLiPSe programs. The next chapter on data structures compares different ways of representing data internally and externally, and presents a canonical multi-representation format which allows effective access to data in all parts of an application. Chapter~\ref{gettingittowork} shows how to convert a high level specification into an executable program early in the development stage. The bulk of the tutorial is contained in chapter~\ref{programmingconcepts}, where we present a number of different programming concepts which can be used as development templates to solve particular problems. This is followed by chapter~\ref{inputoutput} on input/output, a particularly important aspect of developing extensible programs. The last two chapters deal with debugging (chapter~\ref{ifitdoesntwork}) and testing (chapter~\ref{correctnessandperformance}). 116 In this chapter we discuss some high-level design decisions which should be 166 The NDI-Mapper\index{NDI mapper} in RiskWise is an example of the second application type (see figure~\ref{batchtypeapplication}). The application reads some data files (defined in a clear specification), performs some operation on the data and produces results in another set of data files. The top-level query typically just states where the data should be found and where the results should be written to. This batch command \index{batch processing}then internally calls more detailed routines to load data, etc. 207 \section{High level structure} 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. 244 The second high-level design is a data transformation\index{data transformation} structure, used for example in the NDI-Mapper\index{NDI mapper} application. It consists of three parts. 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. 274 We now have an idea of the overall structure of our application and can now turn this into the top-level code structure. We use the module concept of ECLiPSe to clearly separate the components and to define fixed interfaces between them. Each component of our top-level structur [all...] |
/barrelfish-2018-10-04/usr/eclipseclp/documents/internal/kernel/ |
H A D | builtins.tex | 179 Prolog level and definition stored in a table. Character classes and
|
H A D | internal.tex | 91 This is an evolving document, supposed to provide a high level
|
H A D | kernel.tex | 147 Other frequently used data type on the implementation level are: 711 to keep track of the nesting level. Moreover, it is possible that a subterm 713 when switching level up or down. Both these information bits are held in 714 a per level temporary register. 720 read_structure(F,ref(L)) & unify first compound subterm at a nesting level \\ 725 read_list(ref(L)) & unify first list subterm at a nesting level \\ 730 %read_meta(T,ref(L)) & unify first attr variable at a nesting level \\ 735 mode(t(X)) & continue at higher nesting level \\ 748 first & prefix for write first subterm at a nesting level \\ 751 mode(t(X),ref(L)) & continue at higher nesting level, mayb [all...] |
/barrelfish-2018-10-04/usr/eclipseclp/documents/megalog/ |
H A D | intro-sec.tex | 91 This module is the lowest implementation level of the database and knowledge
|
H A D | multiuser-sec.tex | 187 user between relation level and page level locking (see Knowledge Base BIP
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/tutorial/ |
H A D | umsterm.tex | 191 Such clauses occur mainly as input to the top level Prolog loop
|
H A D | umsusing.tex | 88 top-level, which is shown in Figure~\ref{tktop}. 95 \caption{{\tkeclipse} top-level} 100 from the \menu{Help} menu in the top-level window. 277 \guitext{Help} menu on {\tkeclipse}'s top-level window which
|
/barrelfish-2018-10-04/lib/zlib/ |
H A D | trees.c | 931 if (s->level > 0) { 1046 if ((s->last_lit & 0x1fff) == 0 && s->level > 2) {
|
/barrelfish-2018-10-04/usr/eclipseclp/Contrib/ |
H A D | struct.pl | 96 % pretence of being logical (though at the next level up). The next one
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/libman/ |
H A D | extfd.tex | 671 The \eclipse\ debugger is a low-level debugger which is 869 Another reason is that the library performs no meta-level reasoning on 911 The {\bf fd.pl} library defines a set of low-level predicates 1405 We use more or less directly the low-level primitives to handle 1874 If we want to model the containment with low-level domain predicates, 1950 As you can see again, modeling with the low-level domain predicates 1956 some or all constraints with the low-level predicates. 1968 With low-level predicates, 2009 With low-level domain predicates, 2050 A low-level solutio [all...] |
H A D | eplex.tex | 621 low-level interface, for implementing column generation, see 682 This section describes lower level operations like how to set up 683 solvers manually. In fact, these lower level predicates are used to 722 This is an even lower-level primitive, setting up a solver state 766 which would be filtered out by the higher level {\tt lp_add_constraints/3} 817 level predicates that directly access this information via the solver 857 We provide low-level primitives to `expand' an eplex problem. Such a problem is 1461 the {\eclipse} level.
|
/barrelfish-2018-10-04/doc/003-hake/ |
H A D | Hake.tex | 149 a single, top-level file giving symbolic targets. The Makefile 237 Finally, there are two other kinds of high-level construct that Hake 255 The final high-level construct is a ``\texttt{boot}'' - a make target 574 and rebuilds Hake and the top-level Makefile. 693 \item[--verbose:] this option increases the verbosity level of Hake's
|
/barrelfish-2018-10-04/doc/012-services/ |
H A D | Services.tex | 136 provide these services at a minimal level, or provide higher level 473 %% interaction. This is at a higher level than device drivers, and 605 The debugging service needs access to lower level services in order to 972 %% \caption{High level overview of the Barrelfish OS architecture}\label{fig:os-arch}
|
/barrelfish-2018-10-04/doc/013-capability-mgmt/ |
H A D | type_system.tex | 67 CNodes are organized as a two-level table with distinct capability types for 70 The two-level CNode table forms a 32-bit capability address space for each 353 user-level dispatcher. 748 The IRQ table capability allows the holder to configure the user-level 777 This invocation sets the user-level handler endpoint that will receive
|
/barrelfish-2018-10-04/doc/019-device-drivers/ |
H A D | DeviceDriver.tex | 272 level interface to do just that. In the function \fnname{enable\_irq\_mode}, 285 glimpse of the user-level side on writing device drivers for ARM. It consists 446 Note that the discussed PCI API is rather low-level and provides a lot of 495 you a way to have fine grained, page level access control on memory. In 530 want to write user-level device drivers on a new, unsupported platform. We
|
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/ |
H A D | megalog.pl | 369 ** top level 389 MegaLog : buffered I/O level (stream_id = 'C' pointer) 390 Sepia : raw I/O level (stream_id = 0,1,2,...)
|
H A D | elipsys.pl | 544 ** top level 564 MegaLog : buffered I/O level (stream_id = 'C' pointer) 565 Sepia : raw I/O level (stream_id = 0,1,2,...)
|
/barrelfish-2018-10-04/lib/openssl-1.0.0d/crypto/comp/ |
H A D | c_zlib.c | 106 typedef int (*deflateInit__ft)(z_streamp strm, int level, 438 int comp_level; /* Compression level to use */
|
/barrelfish-2018-10-04/usr/drivers/cpuboot/arch/x86/ |
H A D | boot_arch.c | 180 realmodecap.cnode.level = CNODE_TYPE_OTHER;
|
/barrelfish-2018-10-04/usr/eclipseclp/lib_tcl/ |
H A D | tkeclipse.tcl | 1202 balloonhelp .tkecl.pane.answer.label "Results display - top-level bindings and status after execution.\n Results for the most recent query are in blue.\n\
|
/barrelfish-2018-10-04/usr/eclipseclp/lib_tcl/widget/ |
H A D | util.tcl | 667 set name [lindex [info level 0] 0] 797 \"[lindex [info level 0] 0] ?-incomplete? type value\"" 844 return -code error "bad [lindex [info level 0] 0] type \"$type\":\
|