[mercury-users] This Year's Mercury Entry for the ICF 2001 Contest

[Michael Day]

> It's not quite clear to me where 'sh', 'make', or even 'mmc' fit into
> this.

Complicated; they consume a stream and then call other commands and
generate output based on the contents of the input stream.

:- func sh(stream(T)) = stream(derived_from_somehow(T)).

And I haven't considered standard error stream either.

Don't even want to think about programs that manipulate the terminal like
vi or pine.

Rather than assuming that commands like cp can have arbitrary side
effects, it would be nice to have some kind of definition of the
unix filesystem and be able to express the transformations that commands
can have upon it...

Michael

--------------------------------------------------------------------------
mercury-users mailing list
post:  mercury-users at cs.mu.oz.au
administrative address: owner-mercury-users at cs.mu.oz.au
unsubscribe: Address: mercury-users-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-users-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------