apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: apr_proc_wait status codes.
Date Thu, 20 Sep 2001 18:53:54 GMT
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.


----- Original Message ----- 
From: "Bill Tutt" <rassilon@lyra.org>
To: "'Kevin Pilch-Bisson'" <kevin@pilch-bisson.net>; <dev@apr.apache.org>
Sent: Thursday, September 20, 2001 1:26 PM
Subject: RE: apr_proc_wait status codes.

> That would seem to make lots of sense. 
> Bill
> "Though we are not now that strength that in old days moved Earth and
> Heaven, that which we are we are; One equal temper of heroic hearts made
> weak by time and fate but strong in will to strive, to seek, to find,
> and not to yield." -- Tennyson
> -----Original Message-----
> From: Kevin Pilch-Bisson [mailto:kevin@pilch-bisson.net] 
> Sent: Thursday, September 20, 2001 7:50 AM
> To: dev@apr.apache.org
> Subject: apr_proc_wait status codes.
> Hi all,
> I'm the one sort of reponsible for asking for return codes in 
> apr_proc_wait (and thanks for how quickly they were added), but now I am
> concerned about their portability.
> My MSDN page for GetExitCodeProcess says it retrurns either 
> STILL_ACTIVE or the return code for the process.  Meanwhile my linux
> waitpid man page says that the status code must be acessed using
> Perhaps we also need some APR_PROC_STATUS macros?
> -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Kevin Pilch-Bisson                    http://www.pilch-bisson.net
>      "Historically speaking, the presences of wheels in Unix
>      has never precluded their reinvention." - Larry Wall
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

View raw message