[m-rev.] Re: for review: fix bug #20

Ian MacLarty maclarty at csse.unimelb.edu.au
Wed Feb 3 18:21:29 AEDT 2010

On Wed, Feb 3, 2010 at 6:18 PM, Ian MacLarty
<maclarty at csse.unimelb.edu.au> wrote:
> Print a warning when the declarative debugger is about to search in the
> supertree of the starting node and there has been no interaction with the user
> yet (bug #20).  This could happen when the user issues the dd command at a node
> whose descendents are all trusted.  In this case the declarative debugger will
> begin searching in the ancestors of the node where the dd command was issued,
> which can seem unintuitive.  The warning message should help the user
> understand what is going on.
> browser/declarative_debugger.m:
>    Add a warn_if_searching_supertree flag to the declarative debugger state.
>    This flag is initially set to yes and is changed to no after a user
>    interaction.
>    Print a warning if a supertree is requested and there has been
>    no interaction with the user yet.
>    Add a predicate to perform per-session initialization.  This
>    currently resets the warn_if_searching_supertree flag.

Forgot to include this in the log:

    Include the warning message in the expected output.

    New test case.


mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au

More information about the reviews mailing list