[m-dev.] for review: resolving ambiguity in the mdb "break" command

[Fergus Henderson]

On 25-Aug-2000, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> 
> Handle ambiguous procedure specifications in the debugger's "break" command
> more usefully.
...
> 	present the user all the matches for the procedure
> 	specification if their specification matches more than one procedure,
> 	and let them choose whether they want to put a breakpoint on them all,
> 	and if not, which one to put the breakpoint on.
...
>  mdb> break data
> +Ambiguous procedure specification. The matches are:
> +0: pred breakpoints:data/1-0 (det)
> +1: func breakpoints:data/1-0 (det)
> +
> +Which do you want to put a breakpoint on (0-1 or *)? *
>   0: + stop  interface pred breakpoints:data/1-0 (det)
> + 1: + stop  interface func breakpoints:data/1-0 (det)

That change looks good.  I have just one small suggestion: I think it
might be nicer to number the matches starting from 1 rather than from 0.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------