Michael Santos 546ae8890e Correct the stdio functions ...

Sketch for stdin, stdout and stderr. Less specific stdout/stderr
functions will catch the more specific stdout/stderr messages.

For example:

    stdout(Port)

Will match any messages intended for:

    stdout(Port, [Pid0])
    stdout(Port, [Pid0, Pid1])
    stdout(Port, [Pid0, Pid1, Pid2])

This is sort of unavoidable because the port could have called execvp()
and become another process, sending streams of data. BUT, the stream of
data would still need to be prepended with a 2 byte length header (unless
the port changes to using streams and manually parses the length
headers).

2014-03-15 17:55:54 -04:00

..

alcove_call.sh

Split out calls into separate files

2014-03-08 13:30:59 -05:00

alcove_calls.sh

Rename cmd -> call

2014-03-09 09:23:55 -04:00

alcove_version.escript

alcove: sandbox for erlang ports

2014-03-02 08:59:33 -05:00

alcove.escript

Correct the stdio functions

2014-03-15 17:55:54 -04:00