Mail Archives: cygwin/1998/04/21/07:07:57
On 19-Apr-1998, Steve Biskis <mlx AT san DOT rr DOT com> wrote:
> Whats the deal with all those: _<somefunc>_r procedures in the run-time
> that are supposed to protect the "reent" structure and make cygwinb19.dll
> thread-safe ???
>
> I found this in the archives:
My guess is that this documentation is aimed at embedded system developers.
That probably explains the interchangable use of the words
"process" and "thread".
> 3. What is the 2nd way of achieving reentrancy ???
Method 1:
> Use the reentrant versions of the library functions, after initializing a
> global reentrancy structure for each process. Use the pointer to this
> structure as the extra argument for all library functions.
Method 2:
> Ensure that each
> thread of execution control has a pointer to its own unique reentrancy
> structure in the global variable, _impure_ ptr, and call the standard
> library subroutines.
--
Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au> | "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh> | of excellence is a lethal habit"
PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3 | -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -