[m-dev.] for review: stream I/O
Ralph Becket
rbeck at microsoft.com
Tue Oct 3 20:18:31 AEDT 2000
>From Fergus Henderson on 03/10/2000 02:18:54
>
> For a `det' version of the stream interface to be safe,
> it needs to prevent that somehow, either by locking files
> and doing runtime checking, or by limiting expressiveness
> somehow (e.g. the `with_stream' that I proposed).
The with_stream approach, which I definitely think we should
include, has the drawback that one has to know the exact
lifetime of a stream so one can enclose it in the scope of a
with_stream. This isn't always going to be the case, so some
more general mechanism is also required.
--
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
--------------------------------------------------------------------------
More information about the developers
mailing list