[m-rev.] for review: --trace-table-io-all

[Fergus Henderson]

On 02-Sep-2002, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> Make debug grades require tabling of I/O primitives.

Rationale?

> +	% In debugging grades, we want to generate executables in which
> +	% one can do retries across I/O safely.

That comment should also go in the log message, as rationale.

But I'm not yet completely convinced.
Doesn't I/O tabling cost a lot?

Also, is it always desirable?
For programs that just do I/O via the terminal,
it may be nicer to redo the I/O on retries.

Does this actually causes the I/O to be tabled,
or just it just generate executables which are capable of
doing I/O tabling (based on the setting of some mdb option)?

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------