[m-rev.] for review: changes to the library from the mode-constraints branch

[Zoltan Somogyi]

On 19-Aug-2002, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> Well, the wording does seem to suggest the latter, but it is not explicit
> about it, so it is not entirely clear.  A reason to doubt that it means
> that latter is that I don't see how the latter would be useful, given
> that term__var_to_int explicitly leaves the integer values unspecified.

But implementors need not be limited by that fact.

> > > What's the purpose of providing this interface?
> > 
> > It provides information that the mode constraint system can use to batch up
> > some ROBDD operations, making them much more efficient.
> 
> Is the code in the mode constraint system relying on the value returned
> being the maximum in the ordering specified by compare/3?
> Or relying on the values returned by term__var_to_int being
> sequential integers?

The latter, I believe.

Zoltan.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------