Hi, On 21.08.2012 00:11, Boris Schaeling wrote:
On Sat, 18 Aug 2012 23:54:24 +0200, Roland Bock <rbock@eudoxos.de> wrote:
Hi Roland,
[...]But things like wait_for_exit seem strange to me: If the library takes care of the forking and handles setting up pipes in such a nice way, why should the user of the library be bothered with the different ways of interpreting the exit information (unless he really, really wants to)?
can you show me some sample code how you'd like to interpret the exit code?
what about an exit_code class which simply encapsulates WIFEXITED and WEXITSTATUS on Unix and does nothing on windows, like the one attached. I think this would be enough for 95% of all users. And from my point of view the exited() member on windows has sane behavior, too. Regards, Florian Sowade