Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 40278 invoked by uid 500); 16 May 2002 10:35:42 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 40256 invoked from network); 16 May 2002 10:35:42 -0000 X-Authentication-Warning: rdu88-251-253.nc.rr.com: trawick set sender to trawick@attglobal.net using -f Sender: trawick@rdu88-251-253.nc.rr.com To: dev@httpd.apache.org Subject: APLOG_NOERRNO useless From: Jeff Trawick Date: 16 May 2002 06:38:14 -0400 Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N We never do anything with errno in our logging functions. We can figure out whether or not there is an apr_status_t to deal with by comparing the appropriate parameter with 0/APR_SUCCESS only, with no regard to APLOG_NOERRNO. APLOG_NOERRNO made sense before because errno wasn't an explicit parameter. The only conceivable use is so the caller can pass non-zero for the apr_status_t but turn on the APLOG_NOERRNO flag so that no error information is logged. No sleep would be lost here over that feature. -- Jeff Trawick | trawick@attglobal.net Born in Roswell... married an alien...