[m-dev.] streams in Mercury

[Julien Fischer]

On Fri, 16 Dec 2005, Ralph Becket wrote:

> Julien Fischer, Friday, 16 December 2005:
> >
> > Yes, but I wouldn't want it to take three times as long for something
> > that did a large amount of I/O.
>
> But it wouldn't: disc speeds are still much the same, processor speeds
> are up a factor of eight or sixteen!
>
> > > (and given that this experiment was conducted five years ago, I'd wager
> > > that by now the relative difference in user to real time is tiny).
> > >
> >
> > Which was why I asked if anyone had any up-to-date figures further
> > back in this thread.
>
> Pete, can you resolve this one by re-running the test?  Ta!
>
> > > I'd go the other way and vote for the greater generality of the streams
> > > interface and the s/w engineering benefits of not having special-case
> > > code lying around.
> >
> > What special case code?
>
> As I understand it, you're suggesting we duplicate functionality for the
> streams based code and in the IO library.  I'm saying we should just
> implement core functionality in the streams instances and then use
> streams for all things IO.
>

No, I was just misunderstanding what you meant by special case code.

Cheers,
Julien.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------