Searched refs:important (Results 1 - 25 of 62) sorted by relevance

123

/barrelfish-master/usr/eclipseclp/documents/mpslib/
H A Declipse.tex41 important since its applications may be very dynamic in the amount
67 a dramatic effect on the overall performance. It is therefore important
80 are so important that they should be acted upon as quickly as possible. An
87 to differentiate important messages from less important messages. Furthermore,
88 very important messages or {\it exception messages} should not be delayed
93 select the most important messages from a single port with mixture of all
H A Doutline.tex271 important message passing predicates, i.e. allocating/deallocating
288 important difference is that the name server comes into play.
490 We regard the most important issue for the near future is to acquire
/barrelfish-master/usr/slideshow/
H A Dbmp.c48 uint32_t colors, important; member in struct:dib_header
/barrelfish-master/usr/eclipseclp/Kernel/lib/
H A Dhistory.pl43 % Make sure that the important operators are ok
H A Dcalendar.pl315 :- mode month_offset(?, -, -). % clause order important!
/barrelfish-master/usr/eclipseclp/documents/tutorial/
H A Dumsterm.tex167 The most important unit of a Prolog or {\eclipse} program.
H A Dprolog.tex393 It is very important to understand that Logical Variables are
399 The important difference is that the value of a logical variables is
550 It is also important to remember that the scope of a variable
776 %important feature of Prolog. Variables can occur anywhere inside
799 %An important technique using partial data structure is the difference list.
H A Deprolog.tex186 important.}
201 \item The functor is not important
403 The most important \eclipse{}-specific format option is \%w, which
H A Dprogramanalysis.tex133 important areas of information:
H A Dconstimpl.tex303 It is important to understand that this kind of propagation incompleteness
583 we impose the new bounds on the variables. This is important when the
/barrelfish-master/usr/eclipseclp/documents/userman/
H A Dumscmdlineopts.tex110 important library names. The default is \notation{eclipse}.
H A Dumsporting.tex228 it is useful to bear in mind important {\eclipse} features which can make
/barrelfish-master/usr/skb/programs/
H A Dbridge.pl23 % asq: important: this entry _has_ to be here all the time!!
H A Dbridge_postorder.pl25 % asq: important: this entry _has_ to be here all the time!!
H A Dbridge_postorder_sorted.pl29 % asq: important: this entry _has_ to be here all the time!!
H A Dbridge_postorder_sorted_sum.pl29 % asq: important: this entry _has_ to be here all the time!!
H A Dbridge_postorder_sorted_sum_ascending.pl29 % asq: important: this entry _has_ to be here all the time!!
H A Dbridge_postorder_sorted_ascending.pl29 % asq: important: this entry _has_ to be here all the time!!
/barrelfish-master/usr/eclipseclp/documents/applications/
H A Dtutorial.tex104 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.
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}).
171 The critical issue in defining the queries lies in identifying which data are required and/or produced, without building an actual implementation of the system. Another issue is the format of the data, which should allow a simple and efficient implementation without extra overhead for data manipulation. It is most important to get this interface right from the start, as any change will create re-work and problems integrating different versions of the software.
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.
239 It may not be immediately obvious, but it is very important to clearly separate the different phases. For example, it sometimes may seem faster to generate some variables together with the constraints that are set up between them, as this will save at least one scan of the data structure. But at the same time it makes it much more difficult to disable this constraint or to rearrange the constraints in a different order.
422 In this chapter we discuss the choice of data structures for the different application parts. Next to the top-level design, this is the most important aspect that must be specified correctly right from the beginning of a project. The wrong choice of a data structure may mean significant re-work in order to change some deficiency later on, while on the other hand a good data structure design can simplify the coding process and can lead to a very efficient implementation.
548 Experience has shown that the testing\index{testing} and tuning\index{tuning} of an application are by far the most time consuming activities in the development of a LSCO system. It is very important that we prepare test data sets as early as possible, together with some test routines which exercise our API queries with these tests.
616 When adding new parameters it is important to ensure that they are added to all
944 The cuts (!) \index{cut}in the program clauses are very important, a
[all...]
/barrelfish-master/doc/019-device-drivers/
H A DDeviceDriver.tex118 important that the module is not linked like a regular library with the domain,
310 It is important to have at least a minimal a implementation of Octopus for all
499 As a note aside, there are three important memory managers in the system. The
/barrelfish-master/usr/eclipseclp/documents/internal/kernel/
H A Ddebugger.tex156 Mechanism: Trace frames have flags, only the top one is important:
H A Dio.tex181 \item an important distinctions is between output formats that are for
/barrelfish-master/usr/eclipseclp/documents/megalog/
H A Dknowbase-sec.tex164 An important difference to the DB version is that the KB version of the
637 Another important difference between the two types of
/barrelfish-master/doc/008-tracing/
H A DTracing.tex492 important classes that are dealing with getting from trace log data to the
772 it is important that the tracing does not affect measured code too heavily, or
814 disable the appropriate Subsytems, it is also important to know by what degree
/barrelfish-master/usr/eclipseclp/documents/embedding/
H A Dembsumcxx.tex205 destroy the {\eclipse} references. It is important that this

Completed in 129 milliseconds

123