[m-rev.] for review: use proc layouts in annotated trace

[Ian MacLarty]

On 1 Jul 2004, at 15:28, Zoltan Somogyi wrote:

> On 01-Jul-2004, Ian MacLarty <maclarty at cs.mu.OZ.AU> wrote:
>> Zoltan, do you think in light of this it would be best to through an
>> exception if a proc_layout refers to a compiler generated predicate in
>> the declarative debugger, since this shouldn't ever happen?
>
> Not now, but in the future we may need to include unify or compare 
> predicates
> in the annotated trace to provide the proper context for the 
> user-defined
> predicates that they may call.
>
Okay, but in this case we don't want to assume the compiler generated 
predicate is correct since it may call a user defined predicate which 
is incorrect, so I think the code to trust compiler generate predicates 
should be removed for now.  Do you agree?

The oracle should skip questions about compiler generated predicates.  
I need to change the behaviour of skipping so the dd doesn't just abort 
when no answers for a set of questions are given.  Currently this 
behaviour is okay since the dd only searches one level at a time and 
asks about all the children of a node at once, but with binary search 
this won't be the case.

Ian.

--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------