Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 47116 invoked by uid 500); 6 Apr 2000 18:59:24 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 47098 invoked from network); 6 Apr 2000 18:59:23 -0000 Date: Thu, 6 Apr 2000 14:59:20 -0400 (EDT) From: rbb@apache.org X-Sender: rbb@shell.ntrnet.net To: new-httpd@apache.org Subject: Re: Errno code in APR again. In-Reply-To: <00bc01bf9ff9$e7619b70$c1e01b09@raleigh.ibm.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: rbb@shell.ntrnet.net X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > I'd say a system that treated these differently is working in the spirit of > the Unix designers who originally came up with these errnos. Why else would > they have both? So, either the systems that treat these the same are brain > dead or the original designers are brain dead for thinking they needed both > :-). Just kidding of course. Unix design is! Let's not be too judgmental! The two errors are left over from the original split between SVR4 and BSD. Most modern versions of Unix have combined these to be the same error. I thoroughly dislike the fact that we have to compensate for it. Why didn't we have this problem in 1.3? Everything I am looking at in the 1.3 tree checks for EAGAIN. We have one platform that defines EAGAIN to be EWOULDBLOCK in ap_config.h Are we sure this is an actual issue? Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------