[m-dev.] Delayed goals and if-then-else goals

[Fergus Henderson]

On 08-Jan-2004, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> On 07-Jan-2004, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > The right thing for an implementation to do at this point
> > is to _flounder_; that is, to report a run-time error or exception.
> > Well, it is possible that there might be better alternatives,
> > but this is at least the best current practice.
> 
> Floundering when the condition of an if-then-else contains as-yet unproven
> constraints on local variables preserves correctness, but my intuition is
> that it isn't all that useful, because it leads to runtime aborts in too many
> programs.

I would be interested in seeing examples of such programs.

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