From owner-freebsd-hackers Mon Nov 24 15:39:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16333 for hackers-outgoing; Mon, 24 Nov 1997 15:39:27 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16328 for ; Mon, 24 Nov 1997 15:39:24 -0800 (PST) (envelope-from deischen@iworks.InterWorks.org) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id RAA26968; Mon, 24 Nov 1997 17:41:34 -0600 (CST) Message-Id: <199711242341.RAA26968@iworks.InterWorks.org> Date: Mon, 24 Nov 1997 17:41:34 -0600 (CST) From: "Daniel M. Eischen" To: nash@mcs.com Subject: Re: pthread_cond_timedwait returning wrong error? Cc: freebsd-hackers@freebsd.org, julian@whistle.com Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 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? Dan Eischen deischen@iworks.InterWorks.org