Date: Fri, 27 Apr 2012 12:28:25 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin passes through null writes to other software when redirecting standard input/output (i.e. piping)
Message-ID: <20120427162825.GE5625@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <020501cd23f2$20f07620$62d16260$@motionview3d.com> <20120427001718 DOT GA10533 AT ednor DOT casa DOT cgf DOT cx> <jnecv7$ulg$1 AT dough DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <jnecv7$ulg$1@dough.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Sat, Apr 28, 2012 at 12:11:35AM +0900, jojelino wrote:
>On 2012-04-27 AM 9:17, Christopher Faylor wrote:
>> There's no way that Cygwin could know to "skip" a call to WriteFile().
>> Cygwin doesn't interpose itself in the middle of a pipe.  That would be
>> truly disastrous.  If it somehow looked at every pipe read/write rather
>> than just allowing I/O to flow from one end to the other, the mailing
>> list would be even more filled with people complaining that Cygwin is
>> slow.
>>
>Maybe i can measure how much it slowed down after applying the 
>workaround of unworkable runtime of some non-free software.

Thanks for the offer but that presupposes that I'd actually be willing
to go to the effort of coding something up.  I'm really not.

cgf

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