From: "Christopher Nelson" <paradox AT gye DOT satnet DOT net>
To: <djgpp AT delorie DOT com>
Subject: Fw: Libc threading
Date: Wed, 7 Apr 1999 06:52:06 -0600
Message-ID: <01be80f5$716c0500$LocalHost@thendren>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Reply-To: djgpp AT delorie DOT com


-----Original Message-----
From: Christopher Nelson <paradox AT gye DOT satnet DOT net>
To: djgpp AT delorie DOT com <djgpp AT delorie DOT com>
Date: Tuesday, April 06, 1999 9:21 AM
Subject: Libc threading


>I have decided to undertake the task of building a threading mechanism into
>the libc.
>
>This is necessary, not least of all for the X Windows project that our
group
>has undertaken.
>
>My basic plan is this:
>
>    For important variables, e.g. errno, etc. they will be replicated in a
>thread structure.
>    For things that CAN be made re-entrant, they will be made so.
>    A set of hooks will be provided to let threaders communicate with the
>thread mechanism without needing to understand it's internals.
>    A simple interface allows users to spawn threads.  Forking is harder,
>but i would like to TRY to support it, if not real Unix forking, then at
>least a sort of pseudo-fork.
>
>    I'm working with LWP v 2.0 to see what it needs.  I consider it a
fairly
>complete package, it's robust, and it works.  The hooks interface will be
>built around this general idea.  We'll support:
>
>    Semaphores
>    Mutexes
>    Threads
>    Gateways
>    Message Passing
>
>    If anyone would like to help or offer suggestions, please let me know.
>
>                -={C}=-
>
>
>
>
>
>