From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15587 invoked by alias); 2 Apr 2005 17:07:03 -0000 Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sources.redhat.com Received: (qmail 15366 invoked by uid 48); 2 Apr 2005 17:07:00 -0000 Date: Sat, 02 Apr 2005 17:07:00 -0000 Message-ID: <20050402170700.15365.qmail@sourceware.org> From: "jakub at redhat dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20050401163034.814.steelman@post.pl> References: <20050401163034.814.steelman@post.pl> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug libc/814] perror(3) generates an error X-Bugzilla-Reason: CC X-SW-Source: 2005-04/txt/msg00011.txt.bz2 List-Id: ------- Additional Comments From jakub at redhat dot com 2005-04-02 17:06 ------- Hm, why? It will only make glibc slower and bigger. errno value is undefined after most calls, it has defined value only when certain functions signal an error (usually returning -1 or NULL) and only very few functions have errno defined in all cases or unmodified. perror is not one of them. Even if perror preserved errno value, errno is still undefined after write or close that don't return -1. -- What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID http://sources.redhat.com/bugzilla/show_bug.cgi?id=814 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.