Searched refs:analyze (Results 1 - 4 of 4) sorted by relevance
| /barrelfish-master/usr/eclipseclp/Alog/src/ |
| H A D | mergelogs.c | 82 analyze(headerfp);
285 /* analyze: At this point, we have one large sorted file called :tname:.
292 analyze(headerfp) function
330 } /* analyze */
|
| /barrelfish-master/usr/eclipseclp/Kernel/lib/ |
| H A D | modes.pl | 65 the source file to be analysed. The predicate analyze/1 starts the
73 [eclipse 3]: analyze(qsort(++,-)).
83 [eclipse 4]: analyze(qsort(+,-)).
97 :- export analyze/1, analyze_exits/1.
116 analyze(Call) :-
117 analyze(Call, Lookup),
123 analyze(Call, Lookup),
128 analyze(Call, Lookup) :-
1083 writeln("2. analyze a call pattern (e.g. p/2): analyze(
[all...] |
| /barrelfish-master/doc/008-tracing/ |
| H A D | Tracing.tex | 76 you can analyze the trace data using Aquarium 2. Aquarium 2 can be customized with scripts,
78 In addition it supports various export functionalities that allow you to analyze
443 where you can either later analyze it with Aquarium, or with custom scripts.
489 When you analyze trace log data with Aquarium, the main object is a
614 \emph{MUTEX\_LOCK} and \emph{MUTEX\_UNLOCK} pairs -- in order to analyze the
768 analyze trace data, you simply do not start Aquarium, and if you want to analyze
|
| /barrelfish-master/usr/eclipseclp/documents/applications/ |
| H A D | tutorial.tex | 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.
430 \item[data files] The second alternative is to use data files in a fixed format. The ECLiPSe program then has to read these files and build the internal data structures at the same time. Depending on the format, this may require parsing the input format with definite clause grammars (DCG) \index{DCG}\index{definite clause grammar}(see section \ref{howtousedcgs}), adding to the development effort\footnote{ECLiPSEe 5.4 contains a freeware XML (http://www.xml.org) parser which handles most of the detail of parsing XML files. This makes the use of XML as a data exchange format for ECLiPSe are very exiting new possibility. The parser is described in the ``Third Party Library'' section of the reference manual.}. But as the files can be read and written easily, it is quite simple to create test data sets and to analyze problems by hand. The design for the fixed format may require some extra effort if we want to use the full character set for atoms and strings. A proper quoting mechanism may be required in order to distinguish say a comma separator from a comma contained inside a data field.
1814 Suppose we assume that the predicate {\it analyze\_term} is responsible for a problem. We can then simply add a {\it writeln} call before and/or after the predicate call to print out the suspected predicate. The output before that call should show all input arguments, the output after the call should also show the output results.
2213 \item[functor/3] \index{functor/3}define/analyze term for functor and arity
|
Completed in 66 milliseconds