[m-dev.] for review: cleanup of tabling

[Zoltan Somogyi]

> It would be better to put that code next to the existing calls
> to setvbuf(), so that all the changes to the buffering of stdout
> are in the same place.

I removed the new code entirely, and instead enabled the existing code
if either MR_LOWLEVEL_DEBUG or MR_TABLE_DEBUG are defined.

> > runtime/mercury_wrapper.c:
> > 	When debugging tabling, set stdout to be line buffered.
> 
> What's the rationale for that change?

The same as for MR_LOWLEVEL_DEBUG: you don't want the most relevant 
messages about a non-message-generating infinite loop to stay hidden
in a buffer.

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