[Issue 11282] std.process: add capability for two-way inter-process communication without deadlock

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=11282



--- Comment #6 from Hans Fugal <hans at fugal.net> 2013-10-16 16:44:59 PDT ---
Andrei, no you have to buffer all of stdout before you return (and passing all
of stdin before calling is a form of buffering too). 

A source/sink approach would work just fine. Perhaps you can already do that
with ProcessPipes's stdin/stdout/stderr? I'm still ramping up on the rich
stdlib so I'm not sure what constructs but if I had a way to easily plug
p.stdin into some kind of source (maybe a string that already exists, i.e. is
already buffered), and p.stdout into some kind of sink (maybe just a string
that grows (buffers)), and then I have some way to know when it has finished I
can extract the stdout. 

i.e. if it's easy to go string -> process -> string by wiring together a couple
existing classes, then all we have to do is document it.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------