From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19703 invoked by alias); 2 Jun 2005 08:13:18 -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 19657 invoked by uid 48); 2 Jun 2005 08:13:05 -0000 Date: Thu, 02 Jun 2005 08:13:00 -0000 Message-ID: <20050602081305.19656.qmail@sourceware.org> From: "gwesp at flyelite dot ch" To: glibc-bugs@sources.redhat.com In-Reply-To: <20050411165259.840.gwesp@flyelite.ch> References: <20050411165259.840.gwesp@flyelite.ch> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug libc/840] strerror_r() not conforming to SUSv3 X-Bugzilla-Reason: CC X-SW-Source: 2005-06/txt/msg00015.txt.bz2 List-Id: ------- Additional Comments From gwesp at flyelite dot ch 2005-06-02 08:13 ------- Needless to say that for any serious and efficient kind of SW engineering, it is completely out of question to have the user scan the header files (!) in order to be able to find details which should be in the documentation. I acknowledge that I should have defined POSIX_C_SOURCE, but the manual is clearly misleading in that it gives the impression that the GNU version of strerror_r() is the only one present. IMHO the non-standard GNU version should be renamed to gnu_strerror_r() or similar to avoid confusion. Otherwise, hundreds of developers will stumble into the same trap in the future. -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=840 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.