Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Sat, 6 Apr 2002 01:27:45 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: errno.h - EILSEQ Message-ID: <20020406062745.GE12535@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3CABD5A3 DOT A14F32EC AT worldnet DOT att DOT net> <20020404105544 DOT B1475 AT cygbert DOT vinschen DOT de> <3CAE7320 DOT A6B997B8 AT worldnet DOT att DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CAE7320.A6B997B8@worldnet.att.net> User-Agent: Mutt/1.3.23.1i On Fri, Apr 05, 2002 at 10:01:36PM -0600, Dave Trollope wrote: >Since it exists on Linux and Solaris, I figured that this was new to >Cygwin and its applications. The question is, for what was it >introduced to both Linux and Solaris, and shouldn't it be introduced to >Cygwin? That's rarely the question. The question is "Who's going to do the work to get it into Cygwin?" The way to get something into Cygwin is to send a patch. Hopefully, you'd implement both the errno and the code for detecting it, whereever it exists. Otherwise, as Corinna indicates, there is no reason for the errno. If some code is expecting it, without making it conditional, you could easily make a case that THAT code is in error since it's frightfully simple to check for this type of thing. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/