Bug/Weak Implementation? popen* routines can't handle simultaneous read/write?

dmoore damienlmoore at gmail.com
Fri Jun 8 21:14:15 CEST 2007


On Jun 8, 12:30 pm, Nick Craig-Wood <n... at craig-wood.com> wrote:
> Windows has a really strange idea of non-blocking IO - it uses
> something called overlapped io.  You or in the FILE_FLAG_OVERLAPPED
> flag when you create the file/pipe.  You then pass in overlap buffers
> for reading writing.
>

the wx guys appear to do it differently (unless FILE_FLAG_OVERLAPPED
is implicit in the calls they make)

take a look at:
http://cvs.wxwidgets.org/viewcvs.cgi/wxWidgets/src/msw/utilsexc.cpp?rev=1.88&content-type=text/vnd.viewcvs-markup

a reasonably well-documented wxExecute function handles all the messy
win32 api calls and wraps the process in a wxProcess object and the
streams in wxInputStream / wxOutputStream (also see the wxExecuteDDE
function)




More information about the Python-list mailing list