X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 11 Oct 2008 00:52:49 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: optimizing fork/exec in vendor source
Message-ID: <20081011045249.GB15280@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <2cf50a010810092225q1d7190e6k8f8a4f152fce4de4 AT mail DOT gmail DOT com> <48EF48B2 DOT 8070603 AT byu DOT net> <2cf50a010810100626j74c804a4m6ce87dfc0f284505 AT mail DOT gmail DOT com> <20081010142640 DOT GB15821 AT ednor DOT casa DOT cgf DOT cx> <2cf50a010810101850jc21f80bi3c40c816635d8366 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2cf50a010810101850jc21f80bi3c40c816635d8366@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sat, Oct 11, 2008 at 12:50:03PM +1100, Jack Andrews wrote:
>On Sat, Oct 11, 2008 at 1:26 AM, Christopher Faylor <cgf-XXXXXXXXX> wrote:

There is no reason to include my email address in the body of your
message.  That's what email headers are for.

>>>this seems to be an easy problem in cygwin (at least, in comparison to
>>>fork).  and would fix one of the biggest problems with cygwin (or at
>>>least cygwin bash).  who has to hold the copyright?
>>
>> It is not an "easy problem" and there are no guarantees that it would
>> fix anything.
>
>i'm naive when it comes to cygwin internals, but the obvious similarity
>of posix_spawn to CreateProcess is seductive.  can you give me an
>example of one of the difficulties of implementing posix_spawn in
>cygwin so i don't bother the list anymore?

Sorry, but no.

You have this backwards.  If you are going to be making suggestions, you
should be educating yourself and speaking from knowledge rather than
suggesting that problems are "easy" and then asking someone to prove why
they are not.

It is by no means impossible to implement the POSIX spawn functions but
implementing them fully would require quite a bit of work and you'd still
run into Windows limitations.  You can either take my word for it or
study the subject yourself.  I'm not going to educate you.

The particular code that you probably would want to study is in fork.cc
and spawn.cc.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/