[m-rev.] for review: accurately calculate depth to build subtrees to

[Julien Fischer]

On Fri, 13 May 2005, Ian MacLarty wrote:

> >>>> +	** We can't show progress when building a supertree since we don't
> >>>> +	** know what the final event will be.
> >>> Isn't that behaviour potentially confusing?  If it takes a long time
> >>> to build the supertree, might a user not just assume that something
> >>> has gone wrong with the debugger.  Is it possible to get it to
> >>> display
> >>> some sort of progress indicator, even if it's not like the other one?
> >>
> >> Yes it's possible, but building of supertrees will happen much less
> >> often than
> >> building of subtrees (since once a node has been asserted erroneous,
> >> no more
> >> supertrees need be built).
> >>
> > I think the fact that it will only happen rarely will make the
> > difference in
> > behaviour look more like a bug; however I guess it isn't really all
> > that
> > important.  I was just wondering if was (easily) possible to display
> > something when building the supertrees.
> >
>
> Okay, how about if I'm building a supertree I just print a dot every
> second?  That would be pretty easy to do.  I'll do that and also add a
> summary of how subtrees and supertrees are built to the top of
> mercury_trace_declarative.c and then I'll post the interdiff for
> review.
>
Yes, something like that.  I think that it is important that
the user experience here is consistent (or at least as consistent
as is easily possible.)

Cheers,
Julien.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------