X-Spam-Check-By: sourceware.org
Date: Thu, 7 Jun 2007 10:17:52 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] New package: brltty 3.8
Message-ID: <20070607141752.GB4644@ednor.casa1.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20070606102654.GA11636@calimero.vinschen.de> <announce.20070605230831.GC3356@implementation> <f45rfu$r9r$1@sea.gmane.org> <20070606085100.GA5082@implementation> <4666819A.52A6488D@dessent.net> <20070606192445.GG6500@implementation> <20070606201111.GA2366@ednor.casa1.cgf.cx> <20070607114950.GA3958@implementation> <20070607122642.GA31803@trixie.casa.cgf.cx> <ba40711f0706070704w3486145cr17a1fd82f8132bfa@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ba40711f0706070704w3486145cr17a1fd82f8132bfa@mail.gmail.com>
User-Agent: Mutt/1.5.15 (2007-04-06)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Thu, Jun 07, 2007 at 10:04:26AM -0400, Lev Bishop wrote:
> On 6/7/07, Christopher Faylor wrote:
>> On Thu, Jun 07, 2007 at 07:49:50PM +0800, Samuel Thibault wrote:
> <snip>
>
>> >But when talking about communicating with other applications, we need to
>> >use windows interfaces when the linux API doesn't permit it, shouldn't
>> >we?
>>
>> Only if you can clearly communicate why the linux API doesn't work.  I'm
>> not convinced that this is not just a misconception on your part.
>
> Or to put it another way -- cygwin is rather careful when it comes to
> pipes to make sure that all of these uses work correctly and
> interoperate with with windows:
>
> C:\>dir | less
> C:\>ls | less
> C:\>dir | \windows\system32\more.com
> C:\>ls | \windows\system32\more.com
> $ cmd /c dir | les
> $ ls | less
> $ cmd /c dir | /cygdrive/c/windows/system32/more.com
> $ cmd /c dir | /cygdrive/c/windows/system32/more.com
>
> (ie all 8 combinations of pipe-created-by:{win,cygwin},
> source:{win,cygwin}, sink:{win,cygwin} )
>
> So, the big question is: what does brltty do with pipes that is
> different to the above?

I'm ass*u*me*ing that brltty is using named pipes where it might
have used fifos on linux.  Cygwin's fifo implementation is not
extremely robust so I could imagine some problems there.

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/