[m-dev.] IO tabling

[Julien Fischer]

I've been using the declarative debugger on a problem
with exception analysis and a couple of aspects of IO tabling
have been proving irritating.

1) When the debugger thinks there are too many IO actions it won't
   show me them (is 28 really that many?).  There doesn't seem to
   be a way to browse the IO action in this case.  Would it be possible
   to add a show_io or table_io show command that would display
   a single, specified IO action (or a range thereof.)

2) It would be good if the debugger could be told to turn on IO
   tabling at the boundaries of specified modules. For example,
   something like:

		table_io add_module exception_analysis

  would cause the debugger to turn on IO tabling everytime the compiler
  entered the exception_analysis module, and turn it off again when
  leaving that module.

Cheers,
Julien.

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