/barrelfish-master/usr/eclipseclp/documents/internal/kernel/ |
H A D | io.tex | 31 implemented on top of the operating systems low-level I/O operations. 32 On the implementation level, each stream is described by a stream 40 On the {\eclipse} language level, anonymous streams are identified by
|
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-master/usr/eclipseclp/documents/userman/ |
H A D | umsdebug.tex | 74 \item a \emph{level} that is one higher than that of its parent goal. 202 However the depth level of the RESUME corresponds to the waking situation. 278 \item The second number shows the level or depth of the goal, 280 level increases and after exit it decreases again. The initial level 284 that woke it, the level of a resumed goal may be different from 285 the level the goal had when it delayed. 459 If the textual interactive top-level is used, the commands 463 top-level. 696 command asks for the number of the level t [all...] |
H A D | umsintro.tex | 48 high-level modelling and control language, interfaces to third-party 129 %modify the Prolog top-level loop. 132 %The interface is user-friendly, e.g., in the top-level and in the debugger 134 %The top-level loop does not ask for displaying more alternatives
|
H A D | umsflags.tex | 53 \item[Description : ] Specifies current nesting level of recursive 54 top-level loops. 444 \item[Description : ] The name of the current top-level module. This is the 445 caller module for all queries entered in the top-level loop. 446 By default, this is also shown in the top-level prompt.
|
H A D | umserrors.tex | 249 158 & break level & current toplevel module \\ 250 159 & break level & current toplevel module \\ 543 %asks the user what to do - abort, start a break level, debug, continue or exit.
|
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...] |
/barrelfish-master/usr/eclipseclp/documents/embedding/ |
H A D | ecoptions.tex | 98 top-level execute. It is also the module that goals called from C
|
/barrelfish-master/usr/eclipseclp/Contrib/ |
H A D | flat.pl | 53 good idea for + and *. My solution was to have the top-level
|
/barrelfish-master/kernel/arch/armv8/ |
H A D | syscall.c | 75 uint8_t level = sa->arg3; local 81 return sys_dispatcher_setup(to, root, level, vptr, dptr, run, odptr); 890 uint8_t level = sa->arg3; local 893 return sys_identify_cap(root, cptr, level, cap);
|
/barrelfish-master/usr/drivers/pl390_dist/ |
H A D | main.c | 102 * \param 0 is level-sensitive, 1 is edge-triggered 111 //LH: We can't really handle level triggered interrupts in the kernel 334 static errval_t set_sleep_level(struct bfdriver_instance* bfi, uint32_t level) { argument
|
/barrelfish-master/usr/eclipseclp/Kernel/lib/ |
H A D | tracer.pl | 56 Ports are filtered with of_interest/5 and pre-filtered on engine level: 58 ==invoc && minlevel=<level=<maxlevel && 152 % RedoLevel: at which level the failure was caught, ie the youngest
|
H A D | tracer_tty.pl | 299 get_param_default("jump to level", Depth1, N), 569 j[N] jump to level N (default: parent)\n\ 612 b break level\n\ 758 % N == 0 jump to top-level 1085 current_option(0'b, valid, 'break level').
|
/barrelfish-master/lib/openssl-1.0.0d/ssl/ |
H A D | s3_pkt.c | 1402 int ssl3_send_alert(SSL *s, int level, int desc) argument 1410 if ((level == 2) && (s->session != NULL)) 1414 s->s3->send_alert[0]=level;
|
/barrelfish-master/usr/monitor/capops/ |
H A D | capsend.c | 446 err = monitor_domains_cap_identify(src.croot, src.cptr, src.level, &cap); 595 err = monitor_domains_cap_identify(src.croot, src.cptr, src.level, &cap); 744 err = monitor_domains_cap_identify(capref.croot, capref.cptr, capref.level,
|
/barrelfish-master/usr/replay/ |
H A D | master.c | 498 __print_taskgraph(struct pid_entry *root, int level) argument 502 for (int i=0; i<level; i++) 507 __print_taskgraph(root->children[i], level+1);
|
/barrelfish-master/include/vm/ |
H A D | vm_page.c | 2162 int level; local 2215 else if ((level = vm_reserv_level(m)) >= 0 && 2220 m_inc = atop(roundup2(pa + 1, vm_reserv_size(level)) - 2260 if (level >= 0) { 2285 (level = vm_reserv_level_iffullpop(m)) >= 0) { 2290 vm_reserv_size(level)) - pa); 2312 } else if (level >= 0) {
|
/barrelfish-master/doc/015-disk-driver-arch/ |
H A D | libahci.tex | 7 The intent behind \libahci is to provide an easy-to-use low-level interface to 14 \libahci abstracts the low-level \ac{ahci} operations such as the writing to 255 hardware or user level code has to be notified that these commands failed.
|
/barrelfish-master/lib/devif/backends/net/mlx4/drivers/infiniband/core/ |
H A D | ucma.c | 903 static int ucma_set_option_level(struct ucma_context *ctx, int level, argument 908 switch (level) { 949 ret = ucma_set_option_level(ctx, cmd.level, cmd.optname, optval,
|
/barrelfish-master/usr/eclipseclp/documents/libman/ |
H A D | eplexdiff.tex | 29 There are some differences at the source level between standalone and the 108 No propagation of the bounds is performed at the ECLiPSe level: the bounds
|
/barrelfish-master/usr/eclipseclp/documents/tutorial/ |
H A D | programanalysis.tex | 43 \item[Debugger] Provides a low level view of program 283 coverage counters as explained above, however such a level of detail
|
/barrelfish-master/include/lua/ |
H A D | lua.h | 382 LUA_API int (lua_getstack) (lua_State *L, int level, lua_Debug *ar);
|
/barrelfish-master/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...] |