[m-rev.] for review: improve documentation of --fully-strict

[Peter Wang]

On 2007-09-24, Ian MacLarty <maclarty at csse.unimelb.edu.au> wrote:
> On Fri, Sep 21, 2007 at 01:50:00PM +1000, Ian MacLarty wrote:
> > Estimated hours taken: 0.1
> > Branches: main
> > 
> > compiler/options.m:
> > doc/user_guide.texi:
> > 	Document that --no-fully-strict also replaces det goals that produce
> > 	no outputs with `true' and goals that always fail with `fail'.
> > 
> > 	Also change the documented option to --no-fully-strict instead
> > 	of --fully-strict, because --fully-strict is the default.
> > 	XXX Should it be the default?
> > 

The diff looks fine.

> 
> Does anyone have an answer to the above question,

My guess is that --fully-strict usually matches the programmer's
intention so should be left as the default.

Peter

--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------