From owner-freebsd-hackers Wed Sep 2 00:08:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00887 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 00:08:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00872 for ; Wed, 2 Sep 1998 00:08:29 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id QAA17325; Wed, 2 Sep 1998 16:36:19 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809020702.AAA21352@usr02.primenet.com> Date: Wed, 02 Sep 1998 16:36:17 +0930 (CST) From: "Daniel O'Connor" To: Terry Lambert Subject: Re: Thread calls Cc: tinguely@plains.NoDak.edu, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Sep-98 Terry Lambert wrote: > > So, from what I hear, noone is implementing these calls in FreeBSD's > > libc_r? > There is an OpenLDAP effort, which will necessitate these calls being > implemented and/or the PTHREAD_MUTEX_INITIALIZER going away until FreeBSD > complies with Draft 10 (Standard) pthreads. So, why was the PTHREAD_MUTEX_INITIALIZER thing implemented if it broke the ability to easily check between standards? ie is there a good reason to not back that change out until a more comprehensive set of patches comes along? --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message