This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: WCONTINUED/WIFCONTINUED
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-talk at cygwin dot com
- Date: Sun, 12 Jul 2009 23:07:15 -0400
- Subject: Re: WCONTINUED/WIFCONTINUED
- References: <6910a60907100049x47d2645cl1ce5930fb9034dce@mail.gmail.com> <20090710162020.GA20932@ednor.casa.cgf.cx> <4A5A9B52.7000505@byu.net>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
On Sun, Jul 12, 2009 at 08:26:26PM -0600, Eric Blake wrote:
>According to Christopher Faylor on 7/10/2009 10:20 AM:
>>I should be able to implement this. It shouldn't be too hard*.
>
>What - implementing WIFCONTINUED from scratch is easier than fixing a
>regression in named pipes?
>
>To be honest, you deserve a world of thanks for whatever you can manage
>to get working, in spite of the difficulties in dealing with
>microsoft's arbitrary changes across windows versions. Take as much
>time as you need to get it right!
As I'm sure you know, implementing WIFCONTINUED is MUCH easier than
named pipes because the implementation is entirely Cygwin.
I haven't been idle on the named pipe front but everything I've tried so
far has worked imperfectly. I started using Windows named pipes because
I thought it simplified fifo handling a lot. It's looking now like I
may have to invent some kind of interprocess handshaking to make them
work right but I really really don't want to do that unless I really
really have to.
Thanks for the thanks.
cgf