[m-dev.] call for opinions on promise_same_solutions syntax

[Zoltan Somogyi]

On 02-Mar-2006, Peter Schachte <schachte at csse.unimelb.edu.au> wrote:
>         promise_equivalent_solution_sets [Vars] (
>                 whichever [Vars1] Goal1,
>                 whichever [Vars2] Goal2,
> 		...
> 		Goal
>         )

I think that proposal is a distinct improvement over all the earlier ones.
I am ready to implement it, with one exception: the keywords.

I think "whichever" sounds too much like "whatever", which is what you say
when you want to blow someone off :-( so I think we need another keyword.
Any ideas on a replacement? I am drawing a blank.

"promise_equivalent_solution_sets" is ok, but it is very long; you can't
actually write that if the original code is already significantly indented
or you have long variable names in the list. I propose that we use the
keyword "promise_same_solutions", which means the same, but is shorter.

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