[m-rev.] for review: higher order declarative debugging

[Zoltan Somogyi]

On 02-May-2002, Mark Brown <dougl at cs.mu.OZ.AU> wrote:
> There is still a problem in that the
> declarative debugger back end does not filter out external events for
> higher order calls.

I don't understand this comment. What problem are you referring to?

> +:- type decl_atom_map(V) == tree234_cc(decl_atom, V).
> +

Please don't embed the key type in there. In my change to add I/O actions
to the declarative debugger, I am already distinguishing between decl_atoms
that correspond to exits from those that correspond to calls, since only the
former can have a sequence of associated I/O actions. This means that different
maps in the oracle state have different key types. A definition such as

:- type map_cc(K, V) == tree234_cc(K, V).

would be much more appropriate.

> +% since this is the determinism of compare_representation.  Semidet
> +% predicates, however, are now cc_multi.

That last sentence should be something like

Even predicates that used to be semidet are now cc_multi, since ...

Apart from those comments, the diff is fine. The sooner you commit it,
the fewer conflicts I will get in declarative_oracle.m.

Zoltan.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------