[m-dev.] for review: counter.m

[Robert Ernst Johann JESCHOFNIK]

On Thu, 9 Mar 2000, Zoltan Somogyi wrote:

> +	% counter__allocate(N, Counter0, Counter) takes a counter, and
> +	% returns (a) the next integer to be allocated from that counter,
> +	% and (b) the updated state of the counter.
> +:- pred counter__allocate(int::out, counter::in, counter::out) is det.

Wouldn't it make more sense for a counter to be a unique object? Or at
least allow for it to be unique? It may be desirable to ensure that one
never uses an old value of a counter..


rob

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