The following Quintus predicates which differ from ECLiPSe
predicates are available:
This predicate is dummy, since the ECLiPSe macro facility works on every input term, provided that the flag macro_expansion is set to on.
This predicate is identical to get/2 in ECLiPSe .
This is the normal ECLiPSe help/1 predicate.
This predicate is not available, as Quintus' method of passing the module information to meta predicates differs substantially from the ECLiPSe more general concept of tools (see Section ). Only the operator definition for this functor is available.
This is implemented by declaring the predicates as dynamic, so to obtain more efficient programs it is better to put all clauses of the same procedure into one file (or to concatenate all files where multifile predicates occur).
The property interpreted is not provided. The property exported is returned if the predicate is exported or global. Use of get_flag/3 should be preferred.
There are some differences in the flags, as they are mostly simulated with the ECLiPSe flags:
these predicates are slightly different than in Quintus, see the description of the ECLiPSe statistics/2 predicate. The predicate statistics/2 also accepts all Quintus values in the Quintus mode, but for stack_shifts is always returns zeros. statistics/0 returns only Quintus values when in Quintus mode.
these predicates work with the stdout stream
Note that line_position/2 is not implemented. To perform sophisticated output formatting, printf/2,3 or string streams can be used.