From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: General question on the status of named pipes
Date: Mon, 24 Oct 2011 17:55:00 -0000 [thread overview]
Message-ID: <4EA5A683.5000007@redhat.com> (raw)
In-Reply-To: <CALEg2urgsV9EK9cgbawiDJdvYt4p5wQ8M5b50pvF19=hEitSrg@mail.gmail.com>
On 10/24/2011 06:51 AM, Nathan Thern wrote:
> 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.
Actually, named pipes have _never_ worked, at least according to the
full set of POSIX rules. It's just that some releases had code that
limped along better than in other releases for the particular use cases
you happened to throw at them. cgf is working miracles to get it as far
along as he has, but it's a very tough job to emulate POSIX fifos on top
of windows.
--
Eric Blake eblake@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
--
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
next prev parent reply other threads:[~2011-10-24 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 12:51 Nathan Thern
2011-10-24 17:55 ` Eric Blake [this message]
2011-10-24 18:47 ` Nathan Thern
2011-11-02 3:24 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA5A683.5000007@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).