From owner-freebsd-hackers Mon Nov 24 16:00:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA17709 for hackers-outgoing; Mon, 24 Nov 1997 16:00:20 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA17703 for ; Mon, 24 Nov 1997 16:00:17 -0800 (PST) (envelope-from alex@zen.nash.org) Received: (from alex@localhost) by zen.nash.org (8.8.8/8.8.7) id RAA00771; Mon, 24 Nov 1997 17:59:13 -0600 (CST) (envelope-from alex) Message-Id: <199711242359.RAA00771@zen.nash.org> Date: Mon, 24 Nov 1997 17:59:13 -0600 (CST) From: Alex Nash Reply-To: nash@mcs.com Subject: Re: pthread_cond_timedwait returning wrong error? To: deischen@iworks.InterWorks.org cc: nash@mcs.com, freebsd-hackers@freebsd.org, julian@whistle.com In-Reply-To: <199711242341.RAA26968@iworks.InterWorks.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 24 Nov, Daniel M. Eischen wrote: >> > What does the POSIX spec say about the return value of >> > pthread_cond_timedwait()? >> >> The spec says that the error code is returned from the function >> directly, and not via errno. Unfortunately our threads library >> appears to return -1 and set errno instead. >> >> Alex > > Shall I send a PR against our threads library? Or do we > care that our threads library isn't totally POSIX compliant? I'm going to try and clean up the return values the next chance I get (which is probably this weekend). Feel free to submit a PR if you wish, but I wouldn't bother including diffs -- it'll be as much work to verify the diffs as to actually do the work :) Alex