While I was gonna write fork'n'pipe IPC for the emu module, raster setup
some ecore stubs and got me to complete write it in ecore instead.

ecore_exe_pipe_run(), ecore_exe_pipe_write(), and friends will allow
people to fork of a child process and use it's stdin and stdout to
communicate with it.  I call this fork'n'pipe.

This stuff is not complete, but's it late and I wanna go to bed.  All I
have done so far is to flesh out ecore_exe_pipe_run() a bit more.
Since raster had already committed it as a stub I see no problem with
committing what I already have.

I mention it here, because this is my first commit to E.  Go easy on
the newbie.  B-)

I have no idea what my editor will do to my attempts to follow the E
tabbing preferences.  The bulk of the code I added was cut and pasted
from something else I wrote for a project with different coding
standards.  I will finish massaging it to match E coding standards
tomorrow.

While I tested this stuff from emu, and nothing bad happened, YMMV.  It
currently doesn't do anything useful anyway, so ignore it for now.

Attachment: pgpxWa7YBkEZO.pgp
Description: PGP signature

Reply via email to