Date: Tue, 25 Nov 1997 12:24:36 -0700 (MST) From: Charles Mott <cmott@srv.net> To: Terry Lambert <tlambert@primenet.com> Cc: freebsd-hackers@freebsd.org Subject: Re: pthread_cond_timedwait returning wrong error? Message-ID: <Pine.BSF.3.96.971125122102.25012A-100000@darkstar.home> 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: > > > While we are talking about threads, any comments on PR-4376? > > > > 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. > I was wondering whether maybe errno could be a thread-specific variable rather than global -- mabye via use of a macro. I was looking through libc_r sources, but I couldn't discern what was being done in this regard. To me, having all the *_r reentrant functions is a big nuisance. Charles Mott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971125122102.25012A-100000>