X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: bob 295 To: cygwin AT cygwin DOT com Subject: Re: needed feature in Cygwin fifos Date: Tue, 26 Apr 2011 14:31:19 -0400 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201104261431.21330.icanprogram@295.ca> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com >On Tue, Apr 26, 2011 at 01:34:16PM -0400, bob 295 wrote: >>I recognize that Cygwin fifos are "buggy and not suitable for anything but >>simplest of applications", however in the spirit of seeing if things can be >>improved here is some more test code which illustrates one of the "bugs". >Maybe I need to be clearer: I don't need demonstrations of bugs. I know >what doesn't work. >The fifo layer needs a total rewrite right now. Sending this type of email >is a waste of your time. >cgf Fair enough. Is that total rewrite underway? If so any idea when we'll see a workable version? If not what would it take to expedite things? More developer resources? What type of skillset would you need? Thanks again. bob -- 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