Searched refs:components (Results 51 - 75 of 77) sorted by relevance
1234
/barrelfish-master/usr/eclipseclp/documents/applications/ |
H A D | tutorial.tex | 90 The tutorial uses excerpts from one of applications developed by Parc Technologies to highlight some of the design choices and also to provide code examples taken from real-life components. This application is centered on IP network analysis, so devices like routers and interfaces will occur throughout the example code. A detailed understanding of the application domain should not be required to understand and re-use the examples. 271 It can be helpful to draw a data flow graph\index{data flow graph} of the system as a directed graph, showing the main components as nodes and links between sources and sinks of information. A graph of this form should not contain any cycles, and if many links exist between two nodes, we may have to reconsider the split of functionality between. 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 structure should define a module in one file. We place a {\it module}\index{module} directive at the beginning of the file to indicate the module name. 402 If a system contains many modules, it can be helpful to provide a query which automatically generates the documentation for all files. In RiskWise, there is a module {\it document} \index{document}with an entry point {\it document/0} which creates the complete documentation tree. It uses the built-in predicates {\it icompile/1} and {\it ecis\_to\_htlms/4} to extract the documentation information from the source files and to build the HTML files required. Whenever we add a new module to the source of the application, we have to add its name into the {\it components} list. 405 components(L), 413 components([ 538 If a top-level query has already been revised into smaller components, we can immediately write the body of the top-level predicate calling the individual components in the right order and with the correct parameters. Adding stub definitions of these components again leads to an executable program. 540 Whenever we finish development of some of the components, w [all...] |
/barrelfish-master/lib/libc/gen/ |
H A D | glob.c | 915 (struct xlocale_collate*)__get_locale()->components[XLC_COLLATE];
|
/barrelfish-master/usr/eclipseclp/documents/libman/ |
H A D | obsman.tex | 1766 \item There are 5 types of components: 1801 components 1815 contain the components? 1829 that takes an amount of components packed into a {\bf cont/5} 1838 {\bf solve_bin/2} computes the sum of all components which is necessary 1854 first it tries to match the amount of remaining components with zero 1863 its contents is subtracted from the remaining number of components, 2117 as soon as one of the two components is present:
|
H A D | extpropia.tex | 231 of components in their manufacture, and yields a certain profit.
|
H A D | eplex.tex | 858 considered to have as yet unspecified components in the objective function 885 non-zero components of the column, i.e. coefficients for the expandable
|
H A D | gfd.tex | 551 Gecode. The components not supported by Gecode are indicated by `non-inlined'
|
/barrelfish-master/doc/000-overview/ |
H A D | Overview.tex | 70 Figure~\ref{fig:os-arch} shows an overview of the components of the OS. Each 405 A message transport itself consists of several components: 522 components:
|
/barrelfish-master/usr/eclipseclp/documents/embedding/ |
H A D | embsumcxx.tex | 89 creates an {\eclipse} compound term from the given components.
|
H A D | embed.tex | 492 information between the components coded in the different languages: 501 access to its components when required.
|
H A D | embsumc.tex | 61 creates an {\eclipse} term from the given components.
|
/barrelfish-master/lib/libc/regex/ |
H A D | regcomp.c | 771 (struct xlocale_collate*)__get_locale()->components[XLC_COLLATE];
|
/barrelfish-master/usr/eclipseclp/documents/userman/ |
H A D | umsio.tex | 236 system independent path name syntax, where the components are separated by 534 can be used to break it up into even smaller components.
|
H A D | umsmodules.tex | 46 natural components and to define the interfaces between them.
|
H A D | umstkeclipse.tex | 29 {\eclipse}. It consists of two major components:
|
H A D | umsusing.tex | 661 constituent components into modules --- see chapter \ref{chapmodules}.)
|
H A D | exthsusp.tex | 928 The components of a suspension are:
|
/barrelfish-master/usr/eclipseclp/lib_tcl/widget/ |
H A D | console.tcl | 171 widget create Console -type frame -base text -components {
|
H A D | hierarchy.tcl | 291 widget create Hierarchy -type frame -base canvas -components {
|
/barrelfish-master/usr/eclipseclp/documents/tutorial/ |
H A D | umsusing.tex | 444 probably worth turning the constituent components into modules.)
|
H A D | prolog.tex | 171 structure is an aggregate of a fixed number of components, called its
|
/barrelfish-master/usr/eclipseclp/icparc_solvers/ |
H A D | repair.pl | 1036 % treat the nonlinear components
|
/barrelfish-master/doc/008-tracing/ |
H A D | Tracing.tex | 65 The tracing framework in Barrelfish consists of three major components:
|
/barrelfish-master/usr/eclipseclp/Mercury/ |
H A D | m_tree234.pl | 2382 % The input to the following group of predicates are the components
|
/barrelfish-master/usr/eclipseclp/documents/internal/kernel/ |
H A D | kernel.tex | 1549 Also, they can be decomposed into their components (variable and
|
/barrelfish-master/usr/eclipseclp/documents/intro_paper/ |
H A D | eclipse.tex | 693 The different components of the \ECL system all support the
|
Completed in 125 milliseconds
1234