Re: request for feature: compile and trace information

From: Joachim Schimpf <>
Date: Thu 24 Apr 2003 04:26:05 PM GMT
Message-ID: <>
Thanks Ulrich, theses are good suggestions. As for (1), we don't
have the relevant information from the parser at the point where
the problem is discovered (at the end of the module), so I don't
see a quick way of implementing it. Suggestion (2) should be doable.

-- Joachim

> 1) Sometimes, a small typo causes a compiler warning like
> WARNING: predicate used but not declared or defined in constraint/2 in module eclipse
> These typos can be hard to spot, eg
>     constraint with [id: 0],
> instead of
>     C = constraint with [id: 0],
> But where is the location of this typo?  Imagine several different files where
> the string "constraint" being is used in predicate names as well as in
> comments.  It would be of great help to get the same info as with, eg,
> singleton variables.
> 2) Some of my predicates have many clauses.  If I trace such a predicate, I
> sometimes get confused which clause currently gets executed.  Here, it would
> help to access this information similar to G (print ancestors).

 Joachim Schimpf              /             phone: +44 20 7594 8187
 IC-Parc                     /
 Imperial College London    /
Received on Thu Apr 24 17:26:31 2003

This archive was generated by hypermail 2.1.8 : Wed 16 Nov 2005 06:07:23 PM GMT GMT