[m-dev.] trace goal `state' parameters

Julien Fischer juliensf at csse.unimelb.edu.au
Thu Mar 22 09:32:29 AEDT 2007

On Fri, 16 Mar 2007, Julien Fischer wrote:

> In fact state parameters aren't really as useful as they might seem since
> they are implicitly subject to the same visibility restrictions that
> mutables are.  For mutables these restrictions are what we want** but it
> doesn't really make sense for state parameters.  The logging example in the
> reference manual is a case in point; I would like to be able to refer to the
> logging level in many modules - it is truly global, however mutables are
> (intentionally) module local.  Currently the only way to "export" a mutable
> it to manually introduce access predicates for it in the interface of a
> module.  (This won't work with trace goals since the transformation that
> handles state parameters knows nothing of the manually introduced
> predicates.)


> My choice would be to remove support for state parameters.

Unless there are any objections in the next few days I will go
ahead are remove support for state parameters.

mercury-developers mailing list
Post messages to:       mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions:          mercury-developers-request at csse.unimelb.edu.au

More information about the developers mailing list