apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Pilch-Bisson <ke...@pilch-bisson.net>
Subject Re: apr_proc_wait status codes.
Date Thu, 20 Sep 2001 19:31:57 GMT
On Thu, Sep 20, 2001 at 12:33:06PM -0700, Ryan Bloom wrote:
> On Thursday 20 September 2001 11:53 am, William A. Rowe, Jr. wrote:
> > IMHO, these discrepancies should be hidden by our API.  E.g. we aught to
> > provide both an apr_status_t (with the return results matched up across
> > platforms, and added to our APR_statuses lists) and the processes' exit
> > code.
> >
> > APR_SUCCESS would mean the process _has_ terminated, here's the exit code
> > we can share with you.  IMHO exit code is undefined for all other results.
> 
> Our API already creates APR_CHILD_DONE and APR_CHILD_NOTDONE.  These
> are status codes, which is why APR_SUCCESS doesn't make sense here.  There is
> no success or failure, just status.
>
That's fine, what I wanted was the processes exit_code, which for unix would
probably be the value of WEXITSTATUS(status_code) under unix, and just the 
status code under win32, both of which only be valid under APR_CHILD_DONE.

> 
> Ryan
> 

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Mime
View raw message