[mercury-users] some_of_solutions/2

[Dave Slutzkin]

 --- Mark Brown <dougl at cs.mu.OZ.AU> wrote:
> I agree with Ralph about destroying the declarative semantics.  I have
> some further remarks to add:

<snipped>

Yeah, having thought about this for a while I had sort of come to this
conclusion myself.

The problem is that I am writing a semi-compiler (it takes things that look a
bit like mercury clauses and turns them directly into mercury clauses).  But
I'm adding a little to the semantics - basically, each predicate returns a
set of solution-value pairs, where the value gives an indication of how good
the solution is.  So a top-level call should find all possible solutions to a
predicate (along with values) while a lower-level call will already have a
list of solutions that it should then prune further.

So, obviously, because a top-level call is different, I should be able to
utilise the extra argument that you suggested to differentiate between the
two different meanings in the call.

I think I see the light...

thanks,

Dave Slutzkin.

http://www.sold.com.au - SOLD.com.au Auctions
- 1,000s of Bargains!
--------------------------------------------------------------------------
mercury-users mailing list
post:  mercury-users at cs.mu.oz.au
administrative address: owner-mercury-users at cs.mu.oz.au
unsubscribe: Address: mercury-users-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-users-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------