Port QProcess

[Dmitry A. Kuminov]

Provide an OS/2 version of the QProcess class.

[Dmitry A. Kuminov]

QProcess takes some time. The code is a terrible mess of #ifdefs and unused members, very poor separation of platform independent and dependent code; the Qt3 incarnation was a bit cleaner AFAIR.

Note that I decided to not use a process monitor thread in order to monitor for availability of data/space in stdin/stdout/stderr pipes of the started process. In fact, the monitor code is too complex while such a precise level of notification doesn't seem to be really necessary. A timer that checks pipes every something milliseconds should do the job (Qt4/Win32 uses a 100 ms timer for that).

Or I can actually choose to use libc pipes instead of native pipes... In this case, we'll be able to use socket notifiers for instant notifications (as Qt/Unix? does) at (virtually) no cost because this functionality is already there. Will check this tomorrow.

[Silvan Scherrer]

if possible i would vote for the libc implemantation. as i think socket notifiers are easyer to handle than loops for some checks.

[Dmitry A. Kuminov]

Actually, a timer is a bit simpler than socket notifiers (whcih are in turn simpler than native OS/2 pipes with the event semaphore and a waiting thread) but you are right in that socket notifiers are the cleaner way to go than a timer "loop" and I recall that libc pipes in emx/kLIBC work very well and you can select() on them (I did some testing back then), so let's go that way.

The started native implementation will remain in r71 anyway so we will be able to return back to it if something goes wrong with libc.

[Dmitry A. Kuminov]

Done QProcess using libc pipes in r72.

[Dmitry A. Kuminov]

Together with r73 this may be considered as done (but not widely tested).