[m-rev.] for review: controlling retry across I/O

[Mark Brown]

On 01-Nov-2002, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> On 01-Nov-2002, Mark Brown <dougl at cs.mu.OZ.AU> wrote:
> > On 30-Oct-2002, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> > > trace/mercury_trace_internal.c:
> > > 	Make indirect retries (used only in minimal model grades) use only safe
> > > 	retries.
> > 
> > What is the rationale for this part of the change?  What if the original
> > retry command specified -i or -f?
> 
> This part of the change affects only me, since to a first and second
> approximation, I am the only user of minimal model grades. I prefer safety
> in this instance.
> 
> In the long term, I intend to do away with indirect retries completely, but
> that requires implementing some seriously complex tabling machinery first.

Ok, but a brief comment near the relevant code would be good (otherwise
it looks like a bug).

> Were these all the issues you wanted to raise?

Yes, you can go ahead and commit it now.

Cheers,
Mark.

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