Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!think!ames!amdahl!sri-unix!quintus!ok
From: ok@quintus.UUCP (Richard A. O'Keefe)
Newsgroups: comp.lang.prolog
Subject: Re: :- deterministic (HP Prolog)
Message-ID: <978@cresswell.quintus.UUCP>
Date: 15 May 88 08:34:16 GMT
References: <900@cresswell.quintus.UUCP> <6960006@hpfclp.SDE.HP.COM> <2525@zyx.SE>
Organization: Quintus Computer Systems, Mountain View, CA
Lines: 17

In article <2525@zyx.SE>, bd@zyx.SE (Bjorn Danielsson) explains the
:-deterministic declaration.

HP Prolog sounds a *lot* like PopLog.

> I think a convenient
> "cases" or "cond" macro based on a backtrackable if-then-else is a better
> way to make programs deterministic, since that's often what people *mean*
> when they misuse cut.

I put a "cases" construct into the *.edai versions of C Prolog, but could
never think of anything to do with it.  (I got the idea from LM-Prolog.)
I would very much like to learn how to use this construct.

[I very much doubt that most people *do* mean anything when they use cuts,
 but judging from comp.lang.c there are a lot of C programmers who aren't
 too clear on assignment statements or procedure calls.]