X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Date:	Mon, 24 Oct 2011 07:51:21 -0500
Message-ID:	<CALEg2urgsV9EK9cgbawiDJdvYt4p5wQ8M5b50pvF19=hEitSrg@mail.gmail.com>
Subject:	General question on the status of named pipes
From:	Nathan Thern <nthern AT gmail DOT com>
To:	cygwin <cygwin AT cygwin DOT com>
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

I have several scripts that use named pipes for the purpose of
processing sound files. I use them on both linux and cygwin. After the
switch to cygwin1.7 I converted most of them to the use of tempfiles.
Nevertheless, when encountering old scripts in my archives or when
trying to create efficient new scripts I find myself wishing named
pipes still worked; they are one of the more powerful unix-ish
paradigms.

What's the status/priority of getting named pipes to work in 1.7? And,
just for curiosity's sake, what was the fundamental change in 1.7 that
caused them to stop working? -- They worked great in 1.5.

Cygwin is a great tool, and I'm constantly grateful for it's existence.

regards,
NT

--
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

- Raw text -