delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,KHOP_PGP_SIGNED,KHOP_THREADED,SPF_HELO_PASS,TW_CG,T_RP_MATCHES_RCVD |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <50118958.3080909@dancol.org> |
Date: | Thu, 26 Jul 2012 11:15:52 -0700 |
From: | Daniel Colascione <dancol AT dancol DOT org> |
User-Agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: automatically using pipe_byte for certain EXE's |
References: | <5011587F DOT 1000304 AT gmail DOT com> <50116934 DOT 6010002 AT dancol DOT org> <CE9C056E12502146A72FD81290379E9A43640586 AT ENFIRHMBX1 DOT datcon DOT co DOT uk> |
In-Reply-To: | <CE9C056E12502146A72FD81290379E9A43640586@ENFIRHMBX1.datcon.co.uk> |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.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 |
--------------enig55F003CA77F2E04B9B89E165 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 7/26/12 9:34 AM, Adam Dinwoodie wrote: > Daniel Colascione wrote: >> I still don't know why anyone wouldn't want to use pipe_byte all the tim= e. >=20 > I think that was covered pretty explicitly by cgf in reply to you some ti= me > ago: Cygwin still uses message pipes for ptys in pipe_byte mode, so the first of cgf's reasons doesn't apply. As for the way message pipes "more closely mimic" Linux pipes: I don't see it. What's the difference? And does it matter in practice? Can someone give me an actual example of a problem caused by using byte pipes in the non-pty case? I'm not aware of any. Since message pipes cause problems _in practice_ and byte pipes (which Cygwin lived with for many years) don't seem to cause problems _in practice_, pipe_byte should go away and pipe_byte behavior should be used unconditionally. --------------enig55F003CA77F2E04B9B89E165 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlARiVgACgkQ17c2LVA10VtzwACbBoShJaGWqbwyNKr7iVyJntJD IPwAn23coepoim6NiiiHZd6vczuDltmm =2Bm3 -----END PGP SIGNATURE----- --------------enig55F003CA77F2E04B9B89E165--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |