[m-dev.] for review: stream I/O

[Ralph Becket]

>From Fergus Henderson on 02/10/2000 15:12:14
> These approaches don't have to be mutually exclusive, of course.
> There may be a case for providing all three:
> 	- one to use when you care about the order of side effects

Use explicit handles (e.g. io__streams with io__states)

> 	- one to use when you know that the order of side effects
> 	  won't influence the result

:- pred io__unsafe_fork_io(io__state::uo, io__state::di, io__state::uo) is
det.

mayhap?

> 	- one to use when you don't care about the order of side
> 	  effects, even though they may influence the result

:- pred io__join(io__state::di, io__state::di, io__state::uo) is cc_multi.

Okay, this needs a bit of work...

Ralph

--
Ralph Becket      |      MSR Cambridge      |      rbeck at microsoft.com 

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