Re: Delayed-goals

Hi Nuno,

>that, after a successful goal call eclipse maintains a lot of delayed goals
>related with the constraints imposed inside the goal. Is this behaviour
>normal? Shouldn't eclipse free all the memory?

The most likely reason for this is that your program did not instantiate
all the problem variables. The constraints represented by the delayed goals
are part of your answer: these are the constraints that have not yet been
satisfied, so the answer you got is true subject to these still unsatisfied
constraints being true. 

In this case, it is not correct for ECLiPSe to remove the delayed goals. You
should examine your program and see why there are still unsatisfied 
constraints. 

Note that these goals are only maintained until the end of the query, so if
when you try the next query, the memory would have been recovered: ECLiPSe
always free all memory used during the execution of a query (except for the
non-logical stuff).

There might be other reasons for the dealayed goals being there, but we
would need to know more about what they are.

Cheers,

Kish