This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: use posix_spawn in pexecute


On Tue, Mar 12, 2002 at 08:25:43PM -0500, DJ Delorie wrote:
> 
> I think his point is that the purpose of pexecute() is to let each OS
> decide for itself what the most efficient and/or practical way of
> performing that function is.  It is not up to us to decide a
> platform's implementation of pexecute(), but up to the platform
> maintainer.

I wouldn't have a problem with a pexecute implementation marked #ifdef
__hurd__ that used posix_spawn.  My objection is to penalizing systems
with a fast fork primitive, that happen to have posix_spawn also.

zw


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]