Date: Tue, 25 Nov 1997 13:12:16 -0600 (CST) From: Alex Nash <nash@Mcs.Net> To: Terry Lambert <tlambert@primenet.com> Cc: nash@mcs.com, bradley@dunn.org, freebsd-hackers@freebsd.org Subject: Re: pthread_cond_timedwait returning wrong error? Message-ID: <Pine.BSF.3.95.971125131116.25606G-100000@Jupiter.Mcs.Net> In-Reply-To: <199711251746.KAA02503@usr08.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 Nov 1997, Terry Lambert wrote: > > You are 100% right about the return value being incorrect. > > Unfortunately, this problem is present in many more functions than just > > pthread_join(). > > > > From what I can tell by looking at an old DEC OSF/1 reference on > > pthreads, returning -1 an setting errno is the way things used to work. > > Apparently POSIX has changed that. > > Given that "errno" is a global variable, this is actually a good thing. errno is thread-specific. #define errno (* __error()) Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.971125131116.25606G-100000>