QProcess vs K3Process

[Oswald Buddenhagen]

ok, here is a first implementation of the new kprocess.

the windows support for using a shell is ... well ... TODO. :)

the unix version of selective forwarding could/should be made more
efficient by dup2()ing a dup()e of the respective channel in
setupChildProcess(). but i wanted it to work identically on both
platforms first.

i added an overload to set program + args with one list, as that's the
expected output from KShell::splitArgs() and possibly other sources.

the operator<<()s look a bit weird, but i guess we want to keep that
convenience.

is calling this->QProcess::~QProcess(); safe (in that it does not
actually deallocate the object)? if so, i can even implement
startDetachable()/detach().

kptyprocess is a separate thing. later ...

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kprocess.h
Type: text/x-chdr
Size: 7400 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070606/fae572f0/attachment.h>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kprocess.cpp
Type: text/x-c++src
Size: 7094 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070606/fae572f0/attachment.cpp>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kprocesstest.cpp
Type: text/x-c++src
Size: 821 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070606/fae572f0/attachment-0001.cpp>