From owner-freebsd-hackers Wed Dec 2 08:20:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08748 for freebsd-hackers-outgoing; Wed, 2 Dec 1998 08:20:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08735 for ; Wed, 2 Dec 1998 08:20:12 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA26261; Wed, 2 Dec 1998 11:19:44 -0500 (EST) Date: Wed, 2 Dec 1998 11:19:44 -0500 (EST) From: Daniel Eischen Message-Id: <199812021619.LAA26261@pcnet1.pcnet.com> To: jb@cimlogic.com.au, lists@tar.com, scrappy@hub.org Subject: Re: pthread_cancel() function... Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was under the impression that pthread_cancel was a manditory, > not optional, part of both the POSIX and SS2 specifications. However, > I agree it causes problems when used improperly, and it sure seems > like implementing it is a royal pain in the you know what. I have the guts of it implemented, but just haven't wrapped all (any) of the system calls defined as cancellation points. I put it on the back burner to do other things first. If someone wants to finish it before I get back to it, let me know and I'll try to clean it up and make it available. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message