[m-dev.] for review: big step towards a usable debugger, round 3 (part 1 of 3)

[Fergus Henderson]

On 08-Apr-1998, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> 
> tests/misc_tests/queens.*:
> 	A new test case to test the printing of variables in polymorphic
> 	procedures.

s/misc_tests/debugger/

> New File: scripts/mdb
...
> Help="\
> Name:	mdb - Mercury debugger
> Usage:	mdb executable [<options>]...

I suggest s/executable/<executable>/

> Description:
> 	The arguments of this command form a command line.
> 	If the executable named by this command line is a Mercury program
> 	compiled with --generate-trace, mdb will cause this program to be

I suggest s/--generate-trace/\`--generate-trace'/

> 	executed under the supervision of the Mercury internal debugger.
> 	Otherwise, mdb will execute the command line as if the mdb prefix
> 	weren't there.
> Environment variables:
> 	MERCURY_OPTIONS.
> "
> 
> case $# in
> 	0)	echo "Usage: mdb <executable> [<arg> ...]"
> 		exit 1;;

I suggest appending `1>&2' to the `echo' command here,
to make the output go to stderr.


Apart from the minor issues noted above, part 1 looks fine.

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