[m-dev.] Suggestions for mdb

[Ralph Becket]

I have a few ideas for simple improvements to the debugger.

1. Add a `save' command, or something similar, that dumps the
current set of breakpoints and aliases to a local .mdbrc file.
This would save me a fair bit of hassle when debugging.

2. The print command, or some variant thereof, should act
like `ls' in the browser - e.g. pretty printing to depth 5
or whatever has been set in the browser.

2b. Corollary: it would be nice to be able to set browser
variables in the .mdbrc file.

3. Allow multi-command aliases.  I would like to be able to
set up an alias to, e.g., continue to the next break point then
print out all the variables at that point.  Unfortunately,
`alias cp c; p *' is seen as two separate commands.

Cheers,

Ralph

--
Ralph Becket      |      MSR Cambridge      |      rbeck at microsoft.com 
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------