Files
mercury/doc
Fergus Henderson 9d0fd6601a Add support to mdb for doing the debugger I/O in a different
Estimated hours taken: 4

Add support to mdb for doing the debugger I/O in a different
window to the I/O of the program being debugged.

(TODO: I/O from the browser still goes to the standard I/O streams
rather than the debugger I/O streams.  I will commit that soon
as a separate change.)

runtime/mercury_wrapper.h:
runtime/mercury_wrapper.c:
	Add new runtime options for specifying filenames
	for the mdb I/O streams.

doc/user_guide.texi:
	Document the new options.

trace/mercury_trace_internal.c:
	Add three new variables holding the mdb I/O streams.
	Initialise them based on the option settings.
	Change the code so that all I/O goes through these streams.

trace/mercury_trace_tables.c:
trace/mercury_trace_tables.h:
	Pass a `void *' parameter through MR_process_matching_procedures()
	to the function it calls.  This is needed by mercury_trace_internal.c
	to pass `MR_mdb_in' down to MR_print_proc_id_for_debugger().

runtime/mercury_stack_trace.c:
runtime/mercury_stack_trace.h:
	Add a `FILE *' parameter to MR_print_proc_id_for_debugger().

tests/debugger/Mmakefile:
	When creating the `.out' files, redirect stderr as well as stdout,
	since debugger error messages now go to stderr rather than stdout.
1998-12-17 13:37:19 +00:00
..
1998-10-26 04:11:33 +00:00
1997-08-20 07:43:10 +00:00

This directory contains the source for

	The Mercury user's guide
	The Mercury language reference manual
	The Mercury library reference manual
	The Prolog to Mercury transition guide
	The Mercury frequently asked questions list

The master copy of each document is stored in texinfo format, from which
the info, dvi and html versions are derived automatically.

You can create postscript versions from either the dvi or html versions.
Due to the large spacing in texinfo-generated dvi files, the postscript file
generated from the html (manually via a browser such as xmosaic) will be
considerably shorter than the one derived from the dvi file.

The source for the Mercury library reference manual is generated automatically
from the library source files themselves.